Document SaveAs w/o Opening Worksets

I’m trying to save a workshared/central model but keep running into issues with the “Opening Worksets” dialog appearing when the newly saved file is opened, regardless of what settings or nodes I use. I’m currently trying to use the Document SaveAs node from the GeniusLoci package as that includes an input to “openWorksetsConfiguration” which should allow me to determine how/if the workset dialog appears, but regardless of the setting, the saved file is always populating the “Opening Worksets” dialog. Note that this is occurring for me in Revit 2026.4 w/ dynamo v3.6.1 w/ GeniousLoci 2024.5.29

To further clarify, this is the option that I’m trying to set and ideally, I’d like this to be “All” or “Last Viewed”. Note that this snip is from the options button w/in Revit’s Save As dialog.

It’s a bit hard to get an idea of what’s happening as there are no pinned dropdowns to see what information is being processed. Unfortunately the Genius Loci node does not assist by providing the error messages.

The lower SaveAs node will default to user specify

Reviewing the code it appears to only save the first document in the list - however as a custom node it may cycle through a list of Documents. You may have to test this

Based on your inputs the node should be saving the file with workset configuration set to ‘AllWorksets’

Perhaps simplify your graph and build back up?

In the API these are the options that can be set on save as. It sounds odd that the worksets list is coming up, but it appears these are the options that should be available:

1 Like

Out of curiousity.

Why make (save) a Central using Dynamo and not the ‘normal’ way?

Thanks for the responses and direction guys. I’ve been testing this with multiple models and will try simplifying what I’m doing and go from there. For reference, the intention with this script is that it’ll upgrade our project “template” files from one version to another..this will be ran thru dynamo multiplayer.

Ok… I LOVE the idea, but I want to express a word of caution here.

Template updates are always problematic due to the new and modified features, UI updates, and Revit file format changes (which are made annually for speed, stability, reliability, fidelity, to enable new features, and to maintain existing ones). Assuming you don’t have a ridiculous number of templates, it is likely safer to do this manually as it ensures that whatever warnings block the process aren’t leaving you with invalid content, or that an informational pop up gets the correct resolution before things error out.

1 Like

I can’t pretend to know everything behind the scenes with this but am treading very lightly. The upgrading of our templates has been tested w/ fully manual process and no warnings are generated. I completely agree that a manual upgrade is safer but we’ve got (6) project templates plus associated detail container files (because we do have most/all disciplines in house), this task can be pretty substantial managed manually. Thanks for the words of caution! I’ll provide an update once I’ve got this issue squared away!!

How often do you need to ‘upgrade’ your templates?

We’re upgrading our templates every time new content is loaded into our previous version of template or details are added or updated in our detail files. Between these items, it’s minimum (1) template for detail file which needs updated daily.

Note that the intention with this process is to eliminate the majority of our effort to maintain the same content in multiple files, until we’ve made a clean break to our new/primary version of Revit. We can make any changes to our R24 templates and detail files, which at the end of the day are upgraded to R26. At some point in the future, once we move our development efforts into the new version, we’ll shut off this script/process and development will only happen in R26.

I got this squared up and believe the issue was due to having a slop in the script. Once I added a passthrough node so that both the save as nodes weren’t running at the same time, the files save as desired. Thanks for the confirmation that what I was experiencing seemed out of place and appreciate the words of caution!

1 Like