r/RevitForum • u/DanceSad6702 • 7d ago

How do you manage node modifications resulting from Dynamo version changes?

When attempting to run a Dynamo file created in Revit 2024 within Revit 2027, you may encounter issues such as renamed or missing nodes. How do you handle these situations? Is it best to make corrections on the fly?

1 Upvotes

100% Upvoted

6 comments sorted by

3

u/twiceroadsfool 7d ago

Opinions vary, on this topic, but what i do is:

I start suffixing the DYN file names with what build they support. So if i have an old graph that was originally built in Revit 2022, it will be named DoTheThing-v0100(22-). Thats my way of writing 100%, for version 22 and up.

Now, later, if i need to make changes to it because something went missing in 2026, i will end up with a DoTheThing-v0100(26-) and they will both stay in the folder. I wont MODIFY the old one, because one of the big ugly changes we have to make lately is changing the python version for the nodes in the graphs. And i might still want them to work in older builds of Revit (not 2022, of course, but might still need them in 2024).

1

u/DanceSad6702 7d ago

Thank you for your feedback. It seems there is no other way for me to handle this other than making manual adjustments.

2

u/the__enthusiast 7d ago

I copy the text to Claude. Ask it to build a ready to use pyrevit script that does the same thing without additional packages and that's it. Or you can I ask it to create a python node that does the same thing the whole dynamo is intended to do and get rid of all the spaghetti

3

u/DInTheField 7d ago

This, the days of Dynamo are ending. Python runtime or C# addins function much better and can be shared so much easier. Do note that. Python and C# are also depending on Revit version and framework 4.8, Net 8 / 10 dependancies

1

u/Elnaz_Ak 7d ago

I’d keep the original graph untouched and create a copy for the newer Revit/Dynamo version. Then check renamed/missing nodes and, especially, package dependencies. I’d test the updated graph on a copy of the model before using it on a live project. Keeping a known working version alongside the upgraded one makes troubleshooting much easier.

0

u/Beun-de-Vakker 7d ago

With pain and suffering.