You’re not the only one experiencing this; the upgrade is certainly worth it though.
The fact of the matter is that the number of Revit, Revit API, Dynamo, Dynamo API, and Dynamo for Revit changes is significant in the last two years. Prior to this set of changes I would argue that the larger Dynamo for Revit user base was quite fortunate in that there were very few changes from Revit 2018 to 2021, and even 2022 wasn’t too bad. Not sure if it there will continue to be big changes in the coming years, but even if it is you’re still coming out ahead if you are smart about how you do things.
The first key is to have a structure for managing your content. I recommend authoring in the oldest version you support, and saving up into the subsequent years. One dyn version for each Revit release should be the goal. This will allow you to make the change once if something need to be different. Ie: use the old if node up to 2022, save up to 2023, get the warning, swap the old if node out in 2023, save the file, save up to 2024 and you don’t have to fix it again as it is already done. Others recommend the opposite direction - oldest to newest - but that’s really personal preference. My choice in old to new is driven by the fact that you likely have a oldest version in mind already, and the graphs you have are more likely to work there then in the newest build.
Once you set up a structure for managing your graph and package libraries you can move onto automating the migration process. My other account has a reply post somewhere where I distributed some tools I built and shared at BiLT last summer which help with stuff like automatically swapping out the if node, changing the graph scale in bulk, adding your tracker or other common nodes, etc… You can use those to do the bulk processing of your library, and build out similar tools for other repeat fixes when they happen. The last tool in that share out is for building playable journals for a graph library, which when run will open a new Revit instance, open the ‘test’ file for the graph, launch Dynamo, open the associated graph, and run the graph. You can then see if the run was completed, confirm the model changes, and do a save as into the ‘in production’ library that the office can just use. If it failed you can fix it before saving, or do a save as to a ‘needs work’ library and come back to it.
I recommend this process is undertaken at each release and update, as well as after any add-in updates or new installations (basically any time you should be testing your Revit environment, which I also recommend doing via journal automation).
This is the post with the zip file containing the bulk update tools - hope it helps.
