Microstrategy Analytics

Logical Views to specify an outer join between two attribute lookup tables when only attributes are on a report Apart from using the VLDB properties to create the left outer join,  article describes how to use the Logical View to specify an outer join between two attribute lookup tables when only attributes are on a report. This method exists as attribute only outer joins will not be generated on their own by the MicroStrategy SQL engine. This is because they are only necessary with r agged/unbalanced hierarchies which are not supported as null attribute IDs are not supported (parent elements with no child elements or child elements with no parents).  Brief instructions are provided using the example below. Consider, two attributes: Parent01 and Child01 have a parent-child relationship. Their Lookup tables are defined, as follows Parent01 Child01 Note that although there are 4 ID values for the attribute Parent01, there is no defined relationship ...

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 tab...