Question & Answer
Question
In a dimension with six alternate hierarchies, I'd like to synchronize in a rule a "Code-Name" alias for C level elements, which are the same thing hierarchy to hierarchy.
For example, in the main Hierarchy, Code "M1000" is a parent that has dozens of children.
M1000
-M1000.01
-M1000.02
-etc...
-M1000.01
-M1000.02
-etc...
The Code is "M1000" and the Name is "Fred", therefore the Code-Name alias is "M1000 - Fred".
In the nonmain hierarchy, I'd like to write a rule that says:
['Code-Name', in AltHierarchyX or all Alt Hierarchies ] =C: DB(Attributes cube of this dimension, <general addressing to base hierarchy> of element, 'Code-Name);
['Code-Name'] = C: (AttrCube, 'Dim':'BaseHier': Element, 'Code-Name');
I'm assuming it isn't possible given it's an alias, since there's no way to know which C: level element in which hierarchy it's referring too and identically named parents in multiple hierarchies that are the same thing cannot share an alias.
If my assumption is true, I can't even do it in a TI on a Hierarchy rebuild because that too would theoretically violate uniqueness.
Therefore, what would be the best practice?
Answer
Our Development team recommends against using aliases in cube rules rather than the 'base' name of the element. The reason is that when alias values change, the system doesn't consider that an event requiring recompilation of rules. We previously had a similar ask. A means of saying in the left side of a rule 'all instances of consolidated element C, regardless of hierarchy', but unfortunately we don't currently support that.
[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSD29G","label":"IBM Planning Analytics"},"ARM Category":[{"code":"a8m3p000000PC7BAAW","label":"Planning Analytics-\u003EArchitect-\u003EModel and Reporting"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
02 April 2023
UID
ibm16967689