Ragged hierarchies in TARGIT InMemory

Ragged hierarchies are very important for things like organisation hierarchies where the "depth" of the hierarchy is very different depending on the organizational chart.

Can you create a ragged hierarchy based on TARGITs InMemory database – and how?



1 comment
  • Support for ragged hierarchies was recently added to TARGIT data modelling for both TARGIT InMemory and relational data sources. This is a simple example using a General Ledger hierarchy.

    The following link shows an alternate example using a Department hierarchy: https://community.targit.com/hc/en-us/articles/360017087617

    To add a ragged hierarchy, some database work is required. For the dimension database table, the hierarchy data path must be added as separate columns for each level in the hierarchy path. In addition, an integer column containing the hierarchy depth for each data row (the number of relevant hierarchy columns for the row) must be added to the table. Two simple examples of accounts with hierarchy paths and hierarchy depths added:

    When the table has been updated with the necessary columns, a dimension is added to the TARGIT data model with levels based on the hierarchy columns. Finally, the depth column is added to the dimension using the dedicated dimension property. The 10 level dimension with the depth property defined:

    In the TARGIT frontend, the difference using the ragged option is shown in the following screenshot with the ragged hierarchy shown in the right:


Please sign in to leave a comment.

Didn't find what you were looking for?

New post