I have opened an Enhancement Request:
https://mingle-portal.us2.prd3.inforcloudsuite.com/v2/CONCIERGE_PRD/?LogicalId=lid://infor.cxp.1&Tab=ERS&ERId=105393
Short description.
In Modeler Relate, Edit Column Properties, when it comes to defining associations between source columns and Level Keys what matters is only the Column Type ("Attribute"), and not the Hierarchy against which the column is targeted. As a consequence, if a source column is only used as the primary key for a Level (not as an additional attribute for any other level), in principle it would be sufficient to let Birst know that the column is an Attribute, without the need of specifying any Hierarchy.
However, the User Interface requires explicitly the Attribute to be targeted against some Hierarchy. This leads to an unclear situation when the column is used as a Level Key for multiple Levels (which happens sometimes - think of a space about Inventory, where there are properties that should be assigned to combinations of both Item and Warehouse, in a specific "Inventory" Hierarchy, and properties that should be assigned to Items only, in a separate "Item" Hierarchy - here, the Item is used both as Level Key for the "Item" Hierarchy and as part of the Level Key for the "Inventory" Hierarchy). Indeed, Birst associates the column to all Levels in the source grain where the column itself is part of the Level Key, although in the column definition the column itself is associated to one single Hierarchy only.
What I propose is that the structure of the Repository.xml be modified so to allow for definition of Attributes which are not explicitly targeted against any Hierarchy.
Please consider endorsing my ER.
Thank you for your attention, and my best wishes for the upcoming holidays.
Enrico