There are only 2 kinds of hierarchy:
Attribute Hierarchies
These are the single level 'Hierarchies' that exist only for a single attribute. The all level exists optionally as well as every member. Not much of a hierarchy really.
User Hierarchies
Zero or more can be created per dimension - if none then the default all level/members attribute hierarchies will be used.
Can come in 2 flavours:
- Natural Hierarchy - lower levels have more levels than higher levels.
- Reporting/ad-hoc Hierarchy - drilldown path between unrelated hierarchies, like gender/age.
In AS drag and drop to arrange attributes into a hierarchy. AS will check to see if the attribute reelationships support the heirarchy.
Parent-Child hierarchies
Make sure to set
MembersWithData property to
NonLeafData for the hierarchy attribute otherwise all members from higher up will be displayed.
The parent key column will be used to build the hierarchy but will contain the value of the key by default, which is useless. To display the name column instead you have to set the key attribute to have its name property set to whatever name column you need, as opposed to change any properties on the parent child attribute.
Prone to poor performance as no aggregations can be built. Perf can deteririate especially with large dimensions crossjoining to other large dimensions.