Hierarchies

To build a hierarchy, start out by adding the first level of the hierarchy in the same manner as you did with a single-attribute dimension.

The next level of the hierarchy is then created by adding another field to the first level.

Typically, you will also want to rename the level/attribute to something with "... Hierarchy".

In this example, we first added Item Category to the already existing Item dimension, and renamed it to Item Hierarchy. Next, we added Item Subcategory and Item as the next levels.

Note: In older versions (prior to the 2024 June version) hierarchies were created in a slightly different way, as described below:

In this way, we now have a two-level hierarchy. The current Name level actually contains country names.

Now we want to add a third level to this hierarchy: Customer names, which is the Name column from the Customer table. However, when we try this, we will probably see this error message:

So, the problem seems to be that we already used Name in this hierarchy – even if that was from a different table.

To overcome this problem, we must include a work-around in our definition of the Name level from the Country_Region table.

The work-around is to include the full [table.column] references in the Namecolumn and Keycolumn properties of the existing Name level:

In this way, we should now be able to add the Name column from the Customer table as the third level of this hierarchy.

Notice, in this screenshot, property settings have been changed to reflect the names on the dimensions, hierarchies and levels.