Ragged Hierarchies in Microstrategy
Explanation | A ragged hierarchy is the one in which the parent or child attribute element of one or more attribute elements are not present in the level immediately above or below the attribute. In short, some attribute elements don't have a relationship with their parent/child attribute. Information in a ragged hierarchy may look like:
Notice that the Esprit and the Diablo have a missing entry for the Branch, but they have one for the corporation.
|
Problem | Ragged hierarchies are not supported by MicroStrategy |
Recommendation | Create entries for the missing attributes. |
Workaround / Solution | Consider the case where the data has the following format:![]()
New entries for the missing attributes should be added to the Branch attribute lookup table. These entries have to keep the one-to-many relationship of the attributes, so they can not share the same ID. As shown below for the above example, the entries should be added to the LU_BRANCH table. Additionally the BRANCH_ID column of the LU_MODEL table must also be updated:
![]()
This can be done with case statements if the nulls properly exist in warehouse tables and the warehouse cannot be changed. If the parent/child tables do not have rows for the attributes in question those rows must be added to be valid.
|
Comments
Post a Comment