SO I am having so many issues with my Dynamo scripts from revit 2023 to revit 2026 is there a better way of fixing the nodes.
Old way open the script and then click on the missing packages and install what it wants.
new way try the old way and nothing works correctly ugh simple things like Archi-Lab even doesnt have a 2026 package unless the 2025 is still functional.
Orchid, data shapes, etc…
Most of the packages have the ? symbol on then so have a green checkmark is this a hint?
Any help to navigate my like 30 scripts would be so much help
Might be time to see exactly how much of the processes within your graphs can be decoupled from external packages to simplify dependencies across versioning.
Are you fairly reliant on packages with zero-touch nodes or is there the opportunity to extract some python code from nodes? Depending on your lacing etc that could get problematic, but it is something to consider. Are you handy with code? or keen to learn how to be handy?
Relying on package managers/creators to update can be tricky sometimes, we are all very busy people it seems (haven’t updated my own one in a while )
Any python advice just sing out, glad to help while my code is compiling
Whilst extracting py code can sometimes work as suggested, it sounds like you’re coming to a choke point in dynamo where it might be time to delve into python.
Takes time but with AI its never been better to try new things in my experience.
I faced similar challenges when python2/3 split off, and learning a bit of python helped me manage out all but the most hardy of packages like datashapes, bimorph etc. (and eventually make crumple).
Moving from Revit 2023 to Revit 2026 is a HUGE leap. Especially in terms of changes. Looking at Dynamo alone, that is a jump from 2.16.x to 3.6.x.
That is several minor release, and a major (2 → 3) release. So (unfortunately) some breakage is bound to occur.
I agree with @Ewan_Opie regarding taking this time to re-evaluate your graphs and migrate them to nodes that are now OOTB (where/when available).
Re: Custom packages. These will definitely need to be audited during your upgrade process. Unfortunately by the looks of it, archi-lab has not been updated in a little bit. I would reach out directly to @Konrad_K_Sobon 's github here and ask nicely - GitHub · Where software is built. (keeping in mind that packages are created most often as a side project, and in the author’s free time)
For each package you have used in your graphs, you will need to take a look and see what is available. Over the last 1-2 years we introduced package compatibility on the package manager, but not all packages have adopted it yet. So the question marks on the PM re: compatibility indicate that the author has not expressed this.
For python nodes in your graphs (custom packages, etc). Extracting the python seems like a good idea at first, but now you would really be on the hook for keeping that up to date. So, for that reason, it is not something I suggest doing.
What kind of workflows do you have and are needing to migrate?
thank you for everyones imput I am noodling them down one by one and as gavin said doing some dabling. my bigest hickup is Data Shapes ugh they had me hooked on the ease and use of the popup boxes. but now some not all of them are messing with me like the SelectModelElementsData. I know I can just use the player and select using the OOTB stuff but using the data shapes has become a staple at the office any advice? Thanks in advance
like I said some not all is messing with me try the SelectModelElementsData and see if you can select multiple elements. the old way was click the button then window select multiple element. then after selected you had to hit the finish on the revit toolbar. now it only lets me select 1 thing. is it a revit not a datashapes thing now. Thanks for the imput and help
it was weird even though the default was false on selecting single. I had to add a boolean set to true and it then worked. I contacted Data Shapes to share my issue. (nice people quick responses)
)
