I’m able to get the worksetId too, my problem is I’m unable to get the workset name because the Revit Workset table is not send (AFAIK) from the connector.
What I’m trying to doin PowerBI is identifying which elements are in the incorrect workset.
I’m not sure the name is currently being transmitted by Speckle.
As a workaround, you could create a spreadsheet where you have WorksetIds and Names and add it as another source in PowerBI, this way you should be able to expand full names for each element…
@teocomi This is a good idea too. But since I have several files, I was thinking of setting a parameter on the elements with the actual workset name using a script, and then reading from there in PowerBI.
Do you think we can have access to the workset table in future releases?
I worked on a PowerBI template and wanted to use the worksetID. The problem you might face is that the ID changes depending on the project. Even if you have the same NAME, it is possible to have two different IDs.
For example.
Project 1:
WorksetID = 401
WorksetName = Steel
Project 2:
WorksetID = 405
WorksetName = Steel
Therefore, working with worksets on PowerBI is possible, but I do not recommend it if you use the same dashboard on multiple projects.
There might be a way to have a universal worksetID, but I haven’t found one.
We’ve recently worked on other parameters where numerical IDs were passed instead of display text; either that could be extended to a workset, or maybe there is already work in that direction. I’ll check and add this request to the existing one if it’s not yet closed.
This was already merged - the original request was for rooms - @connor realised a single change could cover other data types here, but we can look at the same logic to apply to - I think I see Category and Workset would be too.