Question about LDM Labels with multiple attributes...
# gooddata-clouds
Steve Fox
12/18/2023, 10:27 PMQuestion about LDM Labels with multiple attributes like the example given here:
• https://www.gooddata.com/docs/cloud/model-data/concepts/label/
If I want to display the Department Full Name as what is displayed, that would be the default.
How does one indicate/make sure that the ID is what is used when joining the attribute instead of the default value?
Steve Fox
12/18/2023, 11:10 PMFrom my testing it seems like the best advice would be to make the primary the ID, then add the attributes like Name, shortname, etc. to the ID.
Then when someone includes the ID then uses the display as the Name or whatever attribute, you know that the SQL underneath is using the ID instead of the display name in the query.
Steve Fox
12/18/2023, 11:10 PMUnless there is another way to specify the assumed query results...
Steve Fox
12/18/2023, 11:11 PM(using /debug to download the queries and verifying by the way so I'm not guessing at this point.)
m
Moises Morales
12/18/2023, 11:30 PMHi Steve, the label that is set as the default attribute label in the UI is what is used in the query. Unfortunately I am not aware of any method to set a different label.
s
Steve Fox
12/18/2023, 11:38 PMThat makes no sense.
Steve Fox
12/18/2023, 11:38 PMThe default view is what you see in the filters
Steve Fox
12/18/2023, 11:38 PMI’m seeing the opposite.
m
Moises Morales
12/19/2023, 12:37 AMMy mistake I misunderstood your question. Yes, you are right, adding the attributes to the ID would address this. May I know your use case or why is it important the ID is always used when joining the attribute instead of the default value?
s
Steve Fox
12/19/2023, 12:37 AMOur display values can have duplicates.
Steve Fox
12/19/2023, 12:38 AMSo imagine I have two divisions as in the example. Both are named division 1 but have different ids
Steve Fox
12/19/2023, 12:39 AMI don’t want them joined by display values I want to join on discrete entities
Steve Fox
12/19/2023, 1:29 AMUnless I’m missing something with how that works.
t
Tomas Muchka
12/19/2023, 7:19 AMHello Steve, you should start by creating the attribute from a column with unique values (e.g., ID). Then add additional labels. Marking a label as a default one should influence only what is by default displayed in the UI, but should not influence query results. You can double check this by observing the IDs. Attribute ID should be the same as one of the labels, the one used for querying. I'm not aware that this "primary" can be changed once created.
Tomas Muchka
12/19/2023, 7:21 AMI believe this question covers the same situation. https://gooddataconnect.slack.com/archives/C01USCF4S10/p1702475844924909?thread_ts=1702475844.924909&cid=C01USCF4S10
s
Steve Fox
12/19/2023, 11:53 AMI feel this should be added to the documentation and example for labels. The example is not explicit enough.
t
Tomas Muchka
12/19/2023, 11:55 AMI agree. Let me send this feedback to the docs team 👍
👍 1
s
Steve Fox
12/19/2023, 12:01 PMEither way thank you for confirming.