Early Access: The content on this website is provided for informational purposes only in connection with pre-General Availability Qlik Products.
All content is subject to change and is provided without warranty.
Skip to main content Skip to complementary content

Creating drill-down analysis with hierarchies

Defining which groups in your logical model have a hierarchical relationship enables Insight Advisor to offer breakdown analysis along specified hierarchies and better detect dependencies among groups.

Hierarchies enable drill-down breakdowns in recommendations (such as Sales by Product category, Product sub-category, and Product). Hierarchies also help Insight Advisor avoid mixing geographic items in recommendations. For example, creating hierarchies for Supplier County with Supplier City and for Customer Country and Customer City prevents them from being used in erroneous combinations such as Supplier Country and Customer City.

Hierarchies are also used in associative insights to detect dependencies when making selections. For example, selecting Sweden in an Insight Advisor analysis and then having only Swedish city values be selected in another chart that uses the City field.

There two kinds of logical model hierarchies: learned and defined. Learned hierarchies are detected from how fields are linked and used in the data model. For example, the logical model may see the hierarchical link between a city field and a country field and treat them as having a hierarchy. Defined hierarchies are user-created. Defined hierarchies are created and managed in Hierarchies. Hierarchies are optional for business logic.

You can edit or delete defined hierarchies by clicking and selecting Edit or Delete.

You cannot view or modify learned hierarchies in Hierarchies.

Creating hierarchies

  1. Click Create hierarchy
  2. Enter a hierarchy name.
  3. Add groups to the hierarchy in order from lowest level in the hierarchy to the highest level of the hierarchy.
  4. Click Create.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!