You mean you don’t have this option?
Ahh sorry! Yes it worked !
Great trick haha
Thanks a lot
1 Like
Perfect! Anyway, we do have the issue on github still open to try and find a better approach to this
3 Likes
For me it didnt work, I dont knew why?
Hi again i was just wondering if there is some news about the issue because for me changing the name did not fix the problem
1 Like
Ok, thanks for replying. there is another issue the data take a lot of time to charge on power BI i don’t know if this has any relation with the net speed or not？
@gokermu I have also a sujestion to add a tutorial for creating a Template of Power Bi with spekcle vewer and its URL, this way we can change the URL every time we upload a new commit and see the changes, do a compassion or anayse data changes …etc
1 Like
Yep, our PowerBI connector is pretty slow atm. Looking for ways to increase its speed. Its our top priority
2 Likes
@AlanRynne @gokermu Hi, I want to share with you the solution of coloring elements on the power Bi Viewer that i just understood how it works.
So yes we have to change the Name Of Object Data as you sujested but it has to use the logic of speckle path to the parametre.
For example If you have a Room Parameter that you want to use for coloring rooms you have to change the name to the exact path to the parameter value :
So for this example i used a shared parameter that speckle named (dc122b22-8b9f-45c6-ba42-696c3066b8bb) and to get it i used (parameters.the name.value) and it works for all type of parameters
2 Likes
Great you have a solution.
An alternative to the full parameter path is to prepare the speckle stream data with with Power Query prior to visualisation.
→ 
From there it may be a case of expanding the columns listed as containing records and selecting which values to show and hide. Quite a lot of the Speckle object info can be discarded from a data analytics point of view - its data that makes Speckle tick in all the connectors, not for us humans.
Short and boring video just showing that.
2 Likes
@jonathon thanks yes this is even better, and for the real name on revit maybe we can add the Parameters.The Parameter.name this way we can knew the real name of the parameter if we want to use it for selection, and i tried another way for the shared parameters or parameters that changes on speckle i just used an excel exported from Revit with Those parameters and linked them using The elementid
But of course for the viewer it has to be the name on Speckle
The GUID for shared parameters changing is because within Revit this avoids conflicts caused by parameters having the same name in different contexts. Repeated commits from the same model will maintain the same GUID, but different models may have the same named Parameter using a different GUID.
1 Like
@jonathon Yes I understand , I am not questioning this
I just want to share with others, maybe some time it will help other people that’s all.
The speckle connectors are already genius and personally it helped me a lot 
so thank you again
3 Likes