When extending a view where the “base” has a localised label in a localisations .strings file, a LookML error is generated when “localization_level: strict” is specified in the project manifest.
for example:
view: dwh_d_patient_class {
sql_table_name: DWH_AGILITY.D_PATIENT_CLASS ;;
label: "lbl_vw_patient_class"
extension: required
dimension: code {
label: "lbl_dim_patient_class_code"
type: string
sql: ${TABLE}.CODE ;;
}
dimension: name {
label: "lbl_dim_patient_class_name"
type: string
sql: ${TABLE}.NAME ;;
}
#############################################################
# Hidden columns (for join/predicate purposes etc ...) #
#############################################################
dimension: patient_class_sk {
label: "lbl_hidden"
type: number
primary_key: yes
hidden: yes
sql: ${TABLE}.PATIENT_CLASS_SK ;;
}
...
...
...
}
extended as below
include: "/DWH/base/views/dwh_d_patient_class.view.lkml"
view: xtd_dwh_d_patient_class {
extends: [dwh_d_patient_class]
....
}
results in the following LookML error:
Which is strange, since the label is explicitly specified in the “base” view …
I could easily specify the same label in the extend, but that seems redundant and counter-intuitive thinking about the purpose of extends …
Additionally the remark about the “primary_key” dimension shows the same behavior: a dimension is marked as primary key in the “base” view