Running older scripts in Dynamo 3 and up

Hi all,

When trying to run scripts in Dynamo 3. that were created in versions prior to 3, I get the following message

None of the scripts are running at all and they are also not producing any specific warnings, simply nothing happens.
Is there a straightforward fix to this issue or is it a little more involved than what is seen at surface level?

Thanks so much.
Mitch

Hello Mitch,
There are multiple situations to consider for the right answer. Are you using any packages in your script? do you have the right package version for the right environment? Are you talking about scripts that uses only Dynamo nodes or do you have Civil 3D or Revit related nodes? Do you have Python script nodes and the right engine for Python nodes to be functional?

For each of these situation, you may need to do additional steps and we need to know about your situation to give the right answer. In general, you can follow these steps:

  • Dynamo uses Graph Migration Assistant to allow you to prepare your previous generation graphs for Dynamo versions 2.13.x and higher. You can start with that built-in tool that is under Extensions tab. Here is more information.
  • For packages, as in Dynamo 3.0 and higher versions, we switched to a different Python engine, not all package nodes work perfectly if they Python scripts with the old Python engine. To be able to make them work, you need to install DynamoIronPython 2.7 package. This will install the old engine in Dynamo 3.x versions.
  • If you have Revit nodes that uses an old Revit API, you may need to replace them. You can check out Dynamo section in Revit releases to follow these changes.
  • You can also check Dynamo Release notes to follow the deprecated nodes.

As we are trying to be transparent as much as possible for upcoming changes, there are also certain steps that needs to be taken by package authors and users to keep their graphs updated. I hope these steps can be a guide for you.

Hi Mitch,

There are a few different factors to consider before we can give you the right answer. Could you clarify your situation? For example:

  • Are you using any packages in your script, and do you have the correct package versions for your environment?

  • Are your scripts based only on Dynamo nodes, or do they include Civil 3D or Revit-related nodes?

  • Do you have Python script nodes, and is the correct Python engine installed for those nodes to work properly?

Each of these scenarios may require additional steps, so understanding your setup will help us guide you better.

In general, here are some steps you can follow:

  • Graph Migration: Dynamo includes the Graph Migration Assistant to help prepare older graphs for versions 2.13.x and higher. You can find this tool under the Extensions tab.

  • Packages and Python Engine: Starting with Dynamo 3.0, the Python engine changed. Some packages that rely on the old engine may not work as expected. To fix this, install the DynamoIronPython 2.7 package, which brings back the old engine for Dynamo 3.x.

  • Revit Nodes: If your graphs use Revit nodes tied to an older Revit API, you may need to replace them. Check the Dynamo section in Revit release notes for details.

  • Deprecated Nodes: Review the Dynamo API Changes documentation to stay informed about deprecated nodes and upcoming changes.

We aim to be as transparent as possible about future updates but package authors and users may need to take certain steps to keep their graphs current. Hopefully, these guidelines help you get started.

Hi there,

Thanks so much for the response.

Yes I am using the following packages in this script:

As you can see, I do already have DynamoIronPython2.7 installed, but still the process is failing. I am working with Revit in this case, and all older versions of the script are working no problem. If I go into the Data-Shapes nodes for example I see they are using Python 2.7. Do I need to manually adjust those to 3 and load them back in? Will that work?
I’m just a little unsure about how to get this going as there are very little error message letting me know what the issues are. If I am using Data shapes 2019.2.42 as an example, will I just need to upgrade those to the latest package nodes to get it working?

Thanks again for the assistance.

Mitch