Thanks for the suggestions. As a veteran Navisworks jockey a version of this workflow is definitely on my personal wish list for development roadmap.
A version of this is already possible as the xml reports from Navisworks already include elementIds as does the data you can export.
The way I’ve gotten best results are to youse the advanced option on send “aggregate data to first object” and then in PowerBI perform a data join between the xml and the speckle Navisworks data.
—-
Are you already using the Navisworks connector for Speckle? A number of the early issues you mentioned have been resolved already (YZ flipping, full properties export etc.) give it a whirl. Be warned Navis models can be heavy start with smaller selections.
The next step for us will be to cross check what options people have used and make this the new defaults as we progress out of alpha.
—-