Upgrading graphs to Revit 2022

@Michael_Kirschner2 any thoughts on how to assist? It appears packages are defaulting in @truevis 's case to the Built-In location, and re-pathing didn’t help.

@truevis try putting your package path at the top of the list by using the small arrows to the left of the custom node and package paths dialog.
It sounds like you tried to delete the other builtin paths which ended up re-adding them to the start of the list.
A video/gif of what you are doing/seeing in the package path dialog will help.

1 Like

After uninstalling Revit 2022 and cleaning Registry, a new install plus Revit 2022.1.1 Hotfix, I could install Archilab.

It must have fixed the bad path.
It installed in C:\Users\...\AppData\Roaming\Dynamo\Dynamo Revit\2.12\packages\archi-lab.net

1 Like

Even though archi-lab.net is now installed, it is not visible in the Library and its Clear List node is red. It is the most popular Package, according to https://dynamopackages.com/.
So frustrating.


@truevis - A couple of follow-up questions.

  1. Can you try opening your console and letting us know if there is a message about Archi-lab in there? You can do so by going: ViewShow Console

  2. Can you show us the details of the Notification window? (LIttle green circle with numbers in it, next to the Extensions menu. It should have something about Archi-lab in there.

Also, as an alternative node, have you tried List.Clean?

1 - yes:

Welcome to Dynamo!
00:00:00.4880965 elapsed for loading Dynamo main window.
Preparing to load the library resources.
WPF Render Mode: SoftwareOnly
 Dynamo has detected a conflict with a dependency and may be unstable. If any issues are detected, please uninstall addins or packages and contact the provider.: 
 While loading assembly Autodesk.Forge, Version=, Culture=neutral, PublicKeyToken=null, Dynamo detected that the dependency RestSharp, Version=, Culture=neutral, PublicKeyToken=598062e77f915f75 was already loaded with an incompatible version. It is likely that another Revit Addin has loaded this assembly, please try uninstalling other Addins, and starting Dynamo again. Dynamo may be unstable in this state.
It is likely one of the following assemblies loaded the incompatible version:
GregRevitAuth, Greg, DynamoPackages, archilab2021, archilabUI2021
Clearing workspace...

2 - same:

3 - List.Clean is a fine alternative. But I do not see any other of the Archi-lab nodes in the Library.

archilab2021 & archilabUI2021 DLLs don’t seem to be blocked.

1 Like

I learned from Revit 2022 - Dynamo 2.10 - Package not showing up and icons missing - #11 by Konrad_K_Sobon that one has to use a version number ending in “22”. So “2022.212.2922” worked!




I think you can mark this as the solution to this thread for others to find.


This started as a general thread on the challenges of upgrading Dynamo graphs to Revit 2022. How to get archi-lab working is just one of the challenges we have found the solution to.

Hi @truevis - Beyond the Archi-lab install issue, what other challenges are you experiencing?

I have about 40 big graphs to upgrade. One issue is not being able to set section boxes of 3D Views, anymore. See Problem Setting Crop boxes and Section Boxes in Revit 2022 - #28 by truevis . That will take a bunch of refactoring to implement the workaround I found.

Older packages like Lunchbox may not work or install well. I tried to install the latest Lunchbox from 2018. but it does not show up in the Library. (A 2016 version shows up in the Library.)

Switching out depreciated nodes…

It is quite a big task to upgrade but I will get it done.

1 Like

One trick is to copy and paste a whole graph into a new one. It seems to solve the problem of old-version nodes being kept and shown by yellow "!"s in the Workspace References Extension.



1 Like

Thanks for the rundown of challenges @truevis! A few thoughts that may help :nerd_face:

  1. I hear you on the Section Box issue - unsure what this may be resulting from (Guess to ForgeUnits API) but we’re going to take a look our side with @john_pierson and see if there is anything we can do.

  2. Lunchbox hasn’t been updated for a long time by it’s author. Usually package conflicts like this occur with mis-matched dependencies. Do you see a particular error with the Lunchbox nodes from either the Console, Log or Notifications bar? Suggestion, given that it’s no longer updated, is to move away from this package if you can. Most of the functionality is present in many other epic packages (Check out Genius-Loci, Synthesize Toolkit, Ampersand etc.)

  3. You can still keep the Old If Node if you wish, but I do understand seeing Warnings isn’t ideal in this. If you want to quickly navigate around the graph and replace these you can try the Warnamo extension from @keanw. We’re also looking to get something similar in product for real :slight_smile:

1 Like

The Yellow ! is a choice - you get to keep the nodes in that graph, or “upgrade” them to the version installed on your machine :slight_smile: They won’t affect the graph execution.

But… great trick! If green ticks is what you want then this seems an awesome approach :smiley:

If I click on “Keep Installed Version” does that make it like I put in the node from the current version of the package that I have installed? Is it the same as pasteing into a new graph?

Another way to accomplish that is to search my old Packages folder for the node name, then I can attempt to copy or install that folder or package.

Restart Dynamo after copying that folder to the current Packages path…

1 Like

Be careful when replacing If nodes to the new kind. They may give different results.

1 Like

If you use the “Keep Installed Version”, the version that you save the graph with now will be as installed from you, not as received upon first open.

Flow as follows:

  1. Open graph from elsewhere.
  2. Graph contains nodes from Package XYZ in version 1.0
  3. You have Package XYZ in version 2.0
  4. DYN file has logged package version as 1.0, so flags in “Workspace References” that there is a difference
  5. You get to choose to keep the installed version (2.0), or install the specified version (1.0), which would necessitate your Dynamo removing Package XYZ 2.0 and installing Package XYZ 1.0
  6. If you choose to “Keep Installed Version”, you will serialized back to the DYN file that the package has to upgrade from Package XYZ 1.0 to Package XYZ 2.0.
  7. When you pass on that graph to another person, that graph will require them to then have Package XYZ 2.0.

You will want to manually check that the output of the graph is the same in this scenario, as the package author may have changed the logic of that node, but also may have not. Any package version change (i.e. the author adding new nodes) will prompt this.

Yes please do be aware that the new If node has changed how the logic is calculated so in older graphs you’ll need to be aware of this :pray:

Please read more about it on our blog post: Dynamo Core 2.12 Release - Part 1/2 - Dynamo BIM

You should still be able to return the same results as before (Check out [Request for Feedback] If Node - #24 by solamour for pointers), but now we also support a bunch of new use cases.

Yes, I now click on “Keep Installed Version” for all of the old Packages when I upgrade graphs.

I haven’t had problems with that except for Dynamo’s old/new If – I have to test each replacement.

1 Like