Hierarchy / HierarchyBelongsTo function limitations - Upper limit on NodeID value or number of rows that can be processed?

[#1]

Hi,

I'm trying to get a list box containing elements from a hierarchical data structure to display in Tree View mode as a first step, before using a pivot chart to manipulate the data.

I am using the Hierarchy keyword to turn an adjacent nodes hierarchical structure (thoroughly checked for consistency) into an Expanded nodes format in order to use the generated PATH to drive the tree view listbox.

This is all working fine i.e. the PATH is built correctly apart from for some records, where the parent node is not being identified correctly. In these cases the ParentIDs of multiple rows correctly reference the NodeID of their parent all of which are picked up in the base data set, but QlikView seems to not recognise the relationship. In this example we have the top level node, NodeID 55165, and then all the level 2 nodes whose ParentID is 55165.

As can be seen, the parent name is not being found and the second level records are considered as level 1s, even through they clearly reference the parent correctly. The DEPTH on the top level record and the children is 1 for all records in this example.

NB - for troubleshooting purposes I have set the node name to be the reference followed by the name, but the same thing happend if the text alone is used.

My suspicion is that QlikView cannot handle NodeID values greater than a certain value / process more than a certain number of records from the Resident table upon which the Hierarchy function is used. Can anyone confirm or suggest any other reason?

Many Thanks

Virgil Toher

[#2]

Update: I have removed all other Transaction tables from the load script so that the only data loading into the QVW file is the hierarchical data set followed by the Hierarchy function, and now all the expanded node paths are calculated as expected, including for the higher value Node IDs.

This would indicate that it is not the number of records in the hierarchical data set that is causing the problem but the total amount of data loaded. Are there any settings that limit the number of rows that are processed by such functions based on the amount of related data loaded into the QVW?

Many thanks once again in advance for any help.

[#3]

Seems to work OK in QV10 - Must have been a QV9 bug