QlikView Reference Manual.pdf - QlikCommunity - QlikView

All nodes without a parent id or with a parent id not found in the nodeID column will be considered as
roots. Also, only nodes with a connection to a root node - direct or indirect - will be loaded, thus avoiding
circular references.
Additional fields containing the name of the parent node, the path of the node and the depth of the node can
be created.
The syntax is:
Hierarchy (NodeID, ParentID, NodeName, [ParentName], [PathSource],
[PathName], [PathDelimiter], [Depth])(loadstatement | selectstatement)
where
NodeID is the name of the field that contains the node id.
ParentID is the name of the field that contains the node id of the parent node.
NodeName is the name of the field that contains the name of the node.
ParentName is a string used to name the new ParentName field. If omitted, this field will not be created.
PathSource is the name of the field that contains the name of the node used to build the node path.
Optional parameter. If omitted, NodeName will be used.
PathName is a string used to name the new Path field, which contains the path from the root to the node.
Optional parameter. If omitted, this field will not be created.
PathDelimiter is a string used as delimiter in the new Path field. Optional parameter. If omitted, ‘/’ will be
used.
Depth is a string used to name the new Depth field, which contains the depth of the node in the hierarchy.
Optional parameter. If omitted, this field will not be created.
Example:
Hierarchy(NodeID, ParentID, NodeName) Load
NodeID,
ParentID,
NodeName,
Attribute
From data.xls (biff, embedded labels, table is [Sheet1$];
Back to Script Statements and Keywords (page 219).
HierarchyBelongsTo
The hierarchybelongsto keyword is a prefix to the Load (page 246) and Select (SQL) (page 262) statements.
The internal table must be an adjacent nodes table.
Adjacent nodes tables are tables where each record corresponds to a node and has a field that contains a reference
to the parent node. In such a table the node is stored on one record only but can still have any
number of children. The table may of course contain additional fields describing attributes for the nodes.
More details about adjacent nodes tables and expanded nodes tables can be found in the chapter Hierarchies
in section Evaluating the Loaded Data (page 375).
The prefix creates a table containing all ancestor-child relations of the hierarchy. The ancestor fields can then
be used to select entire trees in the hierarchy. The output table usually contains several records per node.
An additional field containing the depth difference of the nodes can be created.
The syntax is:
237