Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
See why IDC MarketScape names Qlik a 2025 Leader! Read more
cancel
Showing results for 
Search instead for 
Did you mean: 
Karim_Khan
Creator III
Creator III

Unable to create Hierarchy

Hi Team,

     I am unable to create hiereachy on the bais of below SQL

KK
1 Reply
el_aprendiz111
Specialist
Specialist

Hi Karim

TBL:

LOAD * Inline

[

SRO_ROW_ID,SOR_POSTN_ID,SRO_FST_NAME,SRO_LAST_NAME,MNGR_POSTN_ID,MNGR_FST_NAME,MNGR_LAST_NAME

1-160-1368, 1-17GAYD6, SOPHIE RODRIGUES, D, 1-17GAYDF, PARAMESHWAR, MORE

1-160-1368, 1-17GAYD6, SOPHIE RODRIGUES, D, 1-17GAYDF, PARAMESHWAR, MORE

1-160-1368, 1-17GAYD6, SOPHIE RODRIGUES, D, 1-17GAYDF, PARAMESHWAR, MORE

1-160-1368, 1-17GAYD6, SOPHIE RODRIGUES, D, 1-17GAYDF, PARAMESHWAR, MORE

1-160-1368, 1-17GAYD6, SOPHIE RODRIGUES, D, 1-17GAYDF, PARAMESHWAR, MORE

1-160-1368, 1-17GAYD6, SOPHIE RODRIGUES, D, 1-17GAYDF, PARAMESHWAR, MORE

1-160-1368, 1-17GAYD6, SOPHIE RODRIGUES, D, 1-17GAYDF, PARAMESHWAR, MORE

1-160-1368, 1-17GAYD6, SOPHIE RODRIGUES, D, 1-17GAYDF, PARAMESHWAR, MORE

1-160-1368, 1-17GAYD6, SOPHIE RODRIGUES, D, 1-17GAYDF, PARAMESHWAR, MORE

1-160-1368, 1-17GAYD6, SOPHIE RODRIGUES, D, 1-17GAYDF, PARAMESHWAR, MORE

1-160-1368, 1-17GAYD6, SOPHIE RODRIGUES, D, 1-17GAYDF, PARAMESHWAR, MORE

1-160-1368, 1-17GAYD6, SOPHIE RODRIGUES, D, 1-17GAYDF, PARAMESHWAR, MORE

1-160-1368, 1-17GAYD6, SOPHIE RODRIGUES, D, 1-17GAYDF, PARAMESHWAR, MORE

1-160-1368, 1-17GAYD6, SOPHIE RODRIGUES, D, 1-17GAYDF, PARAMESHWAR, MORE

1-160-1368, 1-17GAYD6, SOPHIE RODRIGUES, D, 1-17GAYDF, PARAMESHWAR, MORE

1-160-1368, 1-17GAYD6, SOPHIE RODRIGUES, D, 1-17GAYDF, PARAMESHWAR, MORE

1-160-1368, 1-17GAYD6, SOPHIE RODRIGUES, D, 1-17GAYDF, PARAMESHWAR, MORE

];

[VIEW]:

LOAD Distinct

MNGR_LAST_NAME              AS VALUE,

MNGR_LAST_NAME  &   '-MNGR_LAST_NAME' AS NODE_ID,

MNGR_FST_NAME   &   '-MNGR_FST_NAME'  AS PARENT_NODE_ID

Resident TBL;

[VIEW]:

LOAD Distinct

MNGR_FST_NAME              AS VALUE,

MNGR_FST_NAME  &   '-MNGR_FST_NAME'   AS NODE_ID,

MNGR_POSTN_ID  &   '-MNGR_POSTN_ID'   AS PARENT_NODE_ID

Resident TBL;

[VIEW]:

LOAD Distinct

MNGR_POSTN_ID              AS VALUE,

MNGR_POSTN_ID  &   '-MNGR_POSTN_ID'   AS NODE_ID,

SRO_LAST_NAME  &   '-SRO_LAST_NAME'   AS PARENT_NODE_ID

Resident TBL;

[VIEW]:

LOAD Distinct

SRO_LAST_NAME              AS VALUE,

SRO_LAST_NAME  &   '-SRO_LAST_NAME'   AS NODE_ID,

SRO_FST_NAME   &   '-SRO_FST_NAME'    AS PARENT_NODE_ID

Resident TBL;

[VIEW]:

LOAD Distinct

SRO_FST_NAME              AS VALUE,

SRO_FST_NAME  &   '-SRO_FST_NAME'     AS NODE_ID,

SOR_POSTN_ID  &   '-SOR_POSTN_ID'     AS PARENT_NODE_ID

Resident TBL;

[VIEW]:

LOAD Distinct

SOR_POSTN_ID              AS VALUE,

SOR_POSTN_ID  &   '-SOR_POSTN_ID'     AS NODE_ID,

SRO_ROW_ID    &   '-SRO_ROW_ID'       AS PARENT_NODE_ID

Resident TBL;

[HIER]:

Hierarchy(NODE_ID_H,PARENT_NODE_ID_H, ID, PARENT_NAME, NAME,MY_LEVEL)

LOAD

NODE_ID,

NODE_ID   AS NODE_ID_H,

PARENT_NODE_ID  AS PARENT_NODE_ID_H,

VALUE           AS ID,

VALUE           AS NAME

Resident VIEW;

DROP Table VIEW,TBL;