Thanks a lot Angela for the reply. From what I understood of the requirement, the end user should be able to filter down to a specific tag and see the relationship it has with parent/child BOM, as well as other areas like classification and version. End users usually would have data around 1M items, so it is difficult when the designed TGV can't scale up.
When you say SQL query, do you mean a custom render backed by SQL, or pairing a SQL view with a federated item type that the TGV points to? Also — in your linked thread your SQL approach gave a flat view (Level / Document / Parent columns) and you mentioned it didn't show the intermediate levels.
Did you eventually get it to render as an actual tree with the intermediate BOM levels, or is it still the flat table? If you got the tree working, how did you render it, and did it hold up at larger data volumes?
