After creating our Parent-Child dimension (Part 1), we will see in this second part, the different properties of this dimension.
For this, we keep the same example as before : the dimension of the families (Categories) of a product organized according to a descending hierarchy.
Let's go !!!
By default, the value of this property is NonLeafDataVisible, which means that if a member is also its parent, make it visible :
However, if we set the property to NonLeafDataHidden, members who are equal to their parents will be invisible :
This property is effective when the MembersWithData property is set to NonLeafDataVisible, because it removes the ambiguity between parent and child if a member is also its parent by naming the parent member.
For example, setting the value * (Parent) gives the following result:
This property tells us when to consider a member as parent of its hierarchy, according to the following choices:
- ParentIsBlank : Only members with an null or empty parent key are at the highest level of the hierarchy.
- ParentIsSelf : Only members with a parent key equal to the member key are at the highest level of the hierarchy.
- ParentIsMissing : Only members with no parent keys are at the highest level of the hierarchy.
- ParentIsBlankSelfOrMissing : Group all three choices.
By default, the different levels of a hierarchy Parent-Child are named “Level1, Level2…”.
The purpose of ownership NamingTemplate is to give the possibility to create your own naming model.
However, you can rename each level of the hierarchy to call what you want.
Result on an Excel file:
I hope these explanations will be useful for your projects.