Indeed. My use case is that the PK in the problematic view can be referenced by multiple views (a fk) in the explore.I will try to put this together with extends / refinements the best I can and update the thread on how it was solved (worked around).

@kuopazare you suggesting to have a view for every custom named join that has a composite field in it? That would be 20+ extra views for us.LookML is praising the DRY, which is exactly opposite of this and will create a maintenance nightmare edit: I...

Below is a minimally reproducible example of the problem. The model will work on any ANSI SQL compliant database connection.my_model.modelconnection: "!!!CHANGE-ME!!!"label: "Sandbox"explore: project { view_label: "Project" join: contract { view_labe...

Please share your solution, so others with similar issue can benefit as well.My go to solution is to do something like thisExploreLookML code dimension_group: dim__updated { group_label: "Date: Updated" group_item_label: "{% assign tf = _field._name <!-- -->...

I’m not able to reproduce this with AWS Redshift as connection and Looker version 22.10.32.LookML code is exactly as yoursview: test { derived_table: { sql: SELECT 201 AS seconds ;; } dimension: seconds_duration { type: number sql: ${TABLE}.seconds ;...