Well, not a simple question to formulate… but: what’s the top comfort number of elements that Power BI viewer can effectively handle?
We’re working with pretty large models containing thousands of elements, so when I’m putting them into the PBI environment, I’m facing with significant lags (especially while data processing). And what is the way to reduce them? Perhaps some filtering, cleanings etc?
The hardest of hard limits Power BI imposes on all visuals is 30,000 rows. This is the same limit they impose for CSV import/export.
That is not to say that you can’t prioritise the elements passing from the Data Connector to the viewer needs to be as high as the total objects in a commit. The PowerQuery process can prioritise, cleanse and wrangle this to an optimum number.
How can i load less table data? A row is a single instance element i suppose but i don’t want 100% of parameters i want to take only 12 of the hundreds available for any element in Revit, i think takes ages to export to Speckle because the data not the geometry
Hey @RubenRomeroVivancos, welcome to Speckle.
You can customize the data returned from Speckle to PowerBI using a variation of the default query, which defaults to everything.
This exercises your PowerBI muscles a bit.
