What does the new LookupAttribute in Datamodel do?

[RobSharma]

Could you please clarify the purpose and usage of the LookupAttribute on the datamodel definition? I'm not sure if it is a list odf values ?

[gavind]

I got nothing on top of my head for this. But should this be included in the guide by any chance?
_________________
Be at your best, all the time!

[Admin]

Imagine the situation when you have a CountryID field in your Customer table and corresponding CountryName in Country table.
You would like to add both these fields into your model, both with "Country" name but:
* the first one will be shown only in QueryPanel control and will allow users to select country from the list of available ones (via SQL List value editor) and
* the second one should be shown only in ColumnsPanel (to go into SELECT clause in result).

So you add both these fields into your model as attributes of the Customer entity and turn off "Use in result" for the first field and "Use in condition" for the second one.
So far so good. But there is one problem: EntitiesPanel control shows both these fields by default. To prevent this behavior you can link these two fields by "Lookup attribute" property. If they are linked - only one item will be shown in EntitiesPanel but it still will work properly when you try to add this "combined" attribute into columns or into conditions.

That is the main purpose of "Lookup attribute" option.

[ajo4949]

Does the JavaScript library support the Lookup Attribute functionality?

I tried setting the value in the model editor.

When I use the "[Add new column]" or "[Add new condition]" links in the Columns and Conditions panels, everything looks fine. But I'm still getting both attributes listed (with the same name) in my Entities panel.

Am I missing a step? Any thoughts? Thanks!

[ajo4949]

Just tried this in 3.2 JavaScript library, still not working for me.

Any info on whether this should be working and I'm missing a step or if it's not supported would be appreciated.