Dimensions & Hierarchies

In Valsight every Dimension contains a hierarchy, even if there is only one level in this hierarchy.

To understand the Valsight hierarchy and dimension concept, have a look at the built-in Time dimension, which has several Levels: Year, Quarter, Month, Day.

Each of these levels has so called level values., for example "2018" is a level value of the Year level, which is part of the Time dimension.

Time Dime

The hierarchy thereby describes how level values of one level are aggregated into the next level, e.g. it contains the information that Jan-March 2018 belong to Q1 of 2018, which in turn belongs to 2018. Each level in Valsight has a so called "Level Depth" (or distance from root). In the above Time example, Year has the depth 1, Quarter 2, Month 3, and Day 4. There is no technical limit, however we recommend to not use more than 9.

The same concept can be applied to user defined dimensions. You can create for example a Product Dimension with the levels ProductFamily & Product, or an organization hierarchy which contains a Division level, Business Unit level, and Segment level.

Dimension and Level names may only contain regular letters, but no spaces, dashes, - , or symbols. We recommend to let level and dimension names start with an upper case letter. See also: Naming Guidelines.

Best Practices - Structure of Hierarchies

Each level of the hierarchy should be mutually exclusive and collectively exhaustive (MECE principle). In short, that means, that every datapoint that is available on this level should be part of exactly one level entry, especially in summarized data - hence every physical Euro, case, plane or car is part of exactly one level value in each level of the hierarchy.

To illustrate with an example: consider a company operating in 150 countries. In the model, only the 10 most important countries should be available, and all others should be summarized. Following the above rule, the remaining 140 countries must be part of the level as well (collectively exhaustive) and they cannot be stored as "World-Total" as this would include the other 10 countries as well (not mutually exclusive). Hence the level has to contain a value "Rest of world" or similar that contains the values for the 140 countries. If this data is now to be grouped with a region, the "Rest of world" should be broken down by region as well - otherwise the totals on the Region level would be misleading.

Dim-with-RoW

(lightbulb) Every Hierarchy in Valsight contains an "ALL" level, so there is no need to model "World" explicitly.

Creating and Manipulating Dimensions

Valsight has an separate interface for creating and manipulating dimensions (see menu symbol below).

The dimension management interface consists of three pages. At each page, you can rename and delete items by opening the three dot dialog. You can create new items with buttons located on the top right.

1) First page shows all the available dimensions and lets you to create ones, delete them and manipulate their names.

2) After selecting a dimension (e.g. Location), you arrive at page displaying its dimension levels and associated level values. Here you can rename or delete level values. Also, you can create new level values through Excel upload.

3) The configure hierarchy button leads to third page where users can rename the current dimension levels, delete them and create new ones

Further reading

Also have a look at a detailed description about the creation of the dimensions and  detailed description of the manipulation of existing dimensions. Also, advanced users can still use the old Excel upload method to manipulate dimensions.

Was this helpful?

Yes | Somewhat | No