How to add Views to a Publishing set

jagostinho74 · ‎11-23-2023

hello,

I am trying to find how to add views to a Publishing Set and also on how to turn on said Publishing Set to get publishing in the cloud.

Finding that I cannot just use the Viewport.Create method to add the views to the ViewSheetSet as it is not a sheet per se, unless I am reading it wrong.

And I could not also find the property that enables the set to be published to the cloud.

Anyone knows how to do this programatically?

Thanks in advance for your help

Any

Assistant BIM/CAD Manager

Manchester, UK

jeremy_tammik · ‎11-24-2023

Afaik, you select the views and sheets to publish to the cloud manually in the user interface in the publish settings. Unfortunately, I am not aware of any official API access to that.

Jeremy Tammik

Developer Advocacy and Support + The Building Coder + Autodesk Developer Network + ADN Open

jeremy_tammik · ‎11-24-2023

https://help.autodesk.com/view/RVT/2023/ENU/?guid=GUID-A2444193-FCE8-4219-A590-62CA2B8B5C5D

Jeremy Tammik

Developer Advocacy and Support + The Building Coder + Autodesk Developer Network + ADN Open

RPTHOMAS108 · ‎11-26-2023

Via ProjectInfo singleton I see the below extensible storage item with field likely identifying the sheet set used to publish to cloud. You would create view/sheet sets as you normal elsewhere. Not sure what the major/minor fields are for in this schema, that perhaps plays a part in some kind of version control.

I note that when you publish to cloud you select the 2D views to see in the model viewer. So this feature as far as I'm aware does not publish those sheets to separate folders on ACC (which would perhaps be more useful).

jeremy_tammik · ‎11-27-2023

Thank you for the interesting observation. It looks like a simple list of element ids. Its also seems to allow read and write, i.e., it is not impossible to access for other (non-Autodesk) apps and vendors. So, it might be possible to modify. I don't suppose that would be violating any rules, actually.

Jeremy Tammik

Developer Advocacy and Support + The Building Coder + Autodesk Developer Network + ADN Open

RPTHOMAS108 · ‎11-27-2023

Yes I didn't test myself but I assume it points to a view set or views within such.

After accessing the feature via the UI and saving a set the extensible storage is created. It is far easier to set values on extensible storage fields rather than being responsible for managing the lifecycle of the schema itself. It would not be possible to manage the schema in this case due to the vendor id etc.

The main issue is that if the feature has not been accessed then the schema doesn't exist. However I expect in the case of @jagostinho74 (working directly for an end user company rather than independent developer) they can create the schema in the template they use through the official UI feature and then perhaps just manipulate the values within.

Perhaps a comment for the powers that be is that if open schemas like this existed automatically for this and other similar settings upon file creation then we would not need other specific API functionality to deal with the same. Then it just becomes a case of being informed where to find them and how to use them. Although I expect this feature has evolved from an external add-in, which is perhaps why the setting for such exist as they do.