Decomposition tree for API Hierarchy

Thanks for getting back so quickly,

just to clarify the data received is a .csv file extract from the API catalogue

examples of the 2 key fields are shown below (reality is much more complex)

Every API within the Consumes Column, will have an entry in the URI Column

The URI column is the unique field for the dataset (all the other columns describe specific features about the URI).

from a hierachy perspective, i have tried with the table above to show the current situation

For example,

API 4 consumes API 7 (i.e. URI consumes Level 0)

API 7 consumes API 11 and API 12 (i.e. Level 0 consumes Level 1)

API 12 consumes API 1 (i.e. Level 1 consumes Level 2)

API 1 consumes SoR 1 (i.e. Level 2 consumes Level 3)

I have modelled as follows, using cut down replicas of the original table

to a degree this works as I am able to correctly navigate through the decomposition tree

at the Consumer and API URI levels it successfully displays the correct dataset on the Drillthrough page.

The issue comes when i drillthrough from Level 0/1/2/3, as from each oner of these nodes it drills through to the same entry as API URI, where as i want to be able to drill through to the API entry at Level 0/1/2/3 to its equivalent entry in API URI.

Apologies if my description is a bit convoluted