How should we optimally structure "family tree" data?

Anonymous — Wed, 11 Apr 2018 16:56:14 GMT

We have "family tree" style data, for organizations that looks like this.

Parent Company: Chevron Corp

Direct Subsdiaries: Chevron USA, A, B, C, D

Subsidiaries: A1, A2, B1, B2, B3, B4, C1, C2, D

etc

This data is currently in a flat file table. Generally once you hit 5 levels deep we are done. Other data, such as site locations and financial information, can be associated at any level.

We have some flexibility, today, to structure the data in a way that will optimally work with Qlik.

Has anyone encountered this use case before? Are you aware of best practices in terms of the supporting database structure that optimally support connection to BI?

I'm sure we can use drill-down dimensions, but the tricky thing is, we don't always have the same levels of depth as we do in the case of country - state - city. Some organizations will have 1 level, others will have 5.

Re: How should we optimally structure "family tree" data?

rachel_delany — Mon, 16 Apr 2018 01:39:21 GMT

Perhaps a good option would be to have all of the companies within one table and have a 'Parent' column. This way you can set up the code to iterate and join the data as you need.

Re: How should we optimally structure "family tree" data?

marcus_sommer — Mon, 16 Apr 2018 06:43:39 GMT

Maybe this is helpful: Unbalanced, n-level hierarchies

- Marcus

topic How should we optimally structure "family tree" data? in App Development

How should we optimally structure "family tree" data?

Re: How should we optimally structure "family tree" data?

Re: How should we optimally structure "family tree" data?