Hierarchy structure

The visual supports two kinds of hierarchical structures:

1. Id and Parent Id columns

The hierarchy can be established by having the parent-child relationships defined for every row of data. For example: An organization data, a row of data can correspond to an employee in the company.

We need two columns to establish the parent-child relationships:

1. Each of these rows must have a unique identifier column, like the Employee Id.

2. Another column must contain the parent row’s identifier column, like the Manager Id.

The ‘Hierarchy Field’ data field must be populated with the Id column, while the ‘Parent field’ must be populated with the Parent Id column.

The visual now has the hierarchy structure displayed on the canvas:

Note: The Id and PId columns can also be name columns (like Employee Name and Manager Name respectively). Since Name uniqueness cannot be guaranteed, we recommend using unique Id columns like Index columns.

2. Multiple Category Columns

Provide multiple Category Columns in the ‘Hierarchy Field’ to set the hierarchy for the visual, as shown below:

The values in the leaf level will be picked from the data model. Aggregations for the higher levels will be done within the visual.

Aggregation options are available as follows:

Enable ‘Total’ node as the root node for a grand total.

The hierarchy will be plotted as shown below: