I’m working with larger models from Navisworks Manage and pushing them to Speckle using the connector. In the connector, there’s an option to preserve model hierarchy or not.
What are the actual differences in the cloud when choosing either option?
In the viewer, I usually select objects directly and sort the model using parameters, not model trees.
So I’m wondering:
What are the main differences between flattening the model tree versus keeping it for the web-viewer?
And more importantly – can flattening improve performance in Power BI queries when working with Speckle data?
Appreciate any insights from those who’ve explored this!
Uniquely compared to some of the other connectors speckle publishes from properties exist on collections intenally to Navisworks. It IS possible to perform internal data joins in PowerQuery and we have a few threads here on the forum where ive walked through how this is done.
BUT
Nobody has the time to learn arcane data techniques to get the Family Type properties on an object they click in the visual. Flattening being the default behavior is a baked-in opinion in the name of improving UX.
Alright, I’ll definitely stop preserving model hierarchy as I’ve been doing until now. Just to confirm, does this setting have any impact on in-browser viewing or filtering?
The impact is only whether you appreciate your model elements tree faithfully representing the Navis tree. This is why i switched from v2 to v3 which was the default behaviour - the majority workflow was to feed BI in all forms, programmatic, powerbi and others.
There may be some filtering benefits but again i think it will be a user preference to a degree rather than a performance.