No, for my case I do not use dynamo sandbox. I work only in dynamo for Revit
my usual workflow is very similar to the video i sent. I work in dynamo workspace to test, then when i’m happy with the result, I copy nodes and close worksapce. Create new custom node and paste in my content. adjust inputs/outputs etc and save/close
Hello all - We have now a reproducible way to do this internally and have filed a task to address this for the next Dynamo release (2.18). A big thanks to you all for pointing us in the right direction for this
I second Andreas request for a Hotfix pretty please!!
The workaround I am using at the moment is to take a backup copy of my .dyf before opening for editing. After i edit I do a save-as to a temporary location. After saving the file I manually edit the .dyf file using text editor and replace the updated Uuid with the original Uuid from the backup i made. This allows me to copy the new node into my package location and existing .dyn files still recongnise it as the same node.
To be fair I only use this locally in our internal environment since I don’t publish my package Online to the package manager. I don’t know what affect this would have in your published packages?
@solamour I don’t suppose you’d have any insight into whether an updated dynamo will make it’s way into any new Revit 2023 updates? The slow moving cogs of large business have meant we won’t be able to get onto 2024 for a while yet
There have been some amazing dynamo leaps but cant take advantage of them due to being stuck for now on Revit 2023
We’re looking into that now For the Dynamo updates we rely on Revit patch cycles, so we need to piggy-back on top of that.
The tricky thing is the matrix of stuff that Dynamo touches and testing (i.e. Geometry kernel, base Revit API’s, Analytics tools, DLL’s that conflict with other addin’s etc.) meaning that we don’t release features backwards but rather only target bug fixes, stability fixes, performance fixes, memory leaks etc. in ways that are verifiable and tested.
It’s a tricky balance, because we need to be confident that any fix doesn’t make things worse and the further back the Revit version, the more out of sync it becomes.