How to create hierarchy levels in qlikview

[Anonymous]

Hi All,

Please any help in creating hierarchy levels in qlikview will be appreciated:

Below is code in oracle, where LEVEL field is created, which I want to implement in qlikview:

SELECT employee_id, last_name, manager_id, LEVEL

   FROM employees

START WITH manager_id in ('100')

   CONNECT BY PRIOR employee_id = manager_id;

EMPLOYEE_ID LAST_NAME      MANAGER_ID      LEVEL

----------- ------------------------- ---------- ----------

        101 Jane                                 100          1

        108 Greenberg                        101          2

        109 Faviet                               108          3

        110 Chen                                108          3

        111 Sciarra                             108          3

        112 Urman                              108          3

        113 Popp                                 108          3

Thanks in advance:)

Regards

Neetha

[MayilVahanan]

Hi

You can use same Oracle query in Qlikview and create it.

Otherwise, Please refer

Hierarchy and Hierarchy Belongs to

Hierarchies

[Anonymous]

This blog post by Henric and it's links are well worth a read :

     Hierarchies

[awhitfield]

Hi Neetha

There is an example in the QV Help file

Hierarchy

The hierarchy prefix is used to transform a parent-child hierarchy table to a table that is useful in a QlikView data model. It can be put in front of a LOAD or a SELECT statement and will use the result of the loading statement as input for a table transformation.

The prefix creates an expanded nodes table, which normally has the same number of records as the input table, but in addition each level in the hierarchy is stored in a separate field. The path field can be used in a tree structure.

Syntax:

Hierarchy ( NodeID, ParentID, NodeName, [ParentName], [PathSource], [PathName], [PathDelimiter], [Depth] ) (loadstatement | selectstatement)

The input 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 the node can still have any number of children. The table may of course contain additional fields describing attributes for the nodes.

Usually the input table has exactly one record per node and in such a case the output table will contain the same number of records. However, sometimes there are nodes with multiple parents, i.e. one node is represented by several records in the input table. If so, the output table may have more records than the input table.

All nodes with a parent id not found in the node id column (including nodes with missing parent id) 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.

Arguments:

Argument	Description
NodeID	The name of the field that contains the node id. This field must exist in the input table.
ParentID	The name of the field that contains the node id of the parent node. This field must exist in the input table.
NodeName	The name of the field that contains the name of the node. This field must exist in the input table.
ParentName	A string used to name the new ParentName field. If omitted, this field will not be created.
ParentSource	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	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	A string used as delimiter in the new Path field. Optional parameter. If omitted, ‘/’ will be used.
Depth	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, ParentName, NodeName, PathName, '\', Depth) LOAD * inline [

NodeID, ParentID, NodeName

1, 4, London

2, 3, Munich

3, 5, Germany

4, 5, UK

5, , Europe

];

Result:

NodeID	NodeName	ParentID	ParentName	NodeName1	NodeName2	NodeName3	PathName	Depth
5	Europe		-	Europe	-	-	Europe	1
3	Germany	5	Europe	Europe	Germany	-	Europe\Germany	2
2	Munich	3	Germany	Europe	Germany	Munich	Europe\Germany\Munich	3
4	UK	5	Europe	Europe	UK	-	Europe\UK	2
1	London	4	UK	Europe	UK	London	Europe\UK\London

[luciancotea · Accepted solution]

Table1:

Hierarchy(employee_id, manager_id, last_name)

SELECT employee_id, last_name, manager_id, LEVEL

   FROM employees

START WITH manager_id in ('100')

   CONNECT BY PRIOR employee_id = manager_id;

[Anonymous]

Hi Mayil,

Able to create Level using SQL query in qlikview, but when using preceding load on the sql statement, it gives error Level field not found.

Regards

Neetha

[Anonymous]

Hi Lucian,

Do we need to add anything before Hierarchy(employee_id, manager_id, last_name) statement please?

Regards

Neetha

[luciancotea]

No. Assuming that your SQL statement works, this is what you should have in the QlikView script.

[kaushiknsolanki]

Hi Neetha,

You dont need to create any Level in SQL. QlikView will automatically do that.

Find the example attached with this.

Regards,

Kaushik Solanki

[Anonymous]

Hi Lucian,

I am getting error OLEDB read failed.