Archilab keyschedule node

Revit
1

I created a dynamo script, using the archilab keyschedule, node to import excel information into a key schedule in revit 2023.

When I tried to use the same script in 2025, it runs but does not update the key schedule. It shows no errors. When I look at the value in the keyschedule node in 2025 it shows null.

Does anyone know what might have changed in 2025 to make the script stop working?

If anyone has a suggestion on an alternative solution that would be much appreciated

2

Hi @TomHEV9PF try open the node, if i remember that one is in python… and set to cpython 3 or ironpython 3 and see if it could work

3

Sovitek,

That was it!. Thank you. I tried every else but never checked the Python version.

4

Another question, it appears 2023 wants to use IronPythin2.7 2.4.0, Revit 2025 wants to use IronPythin2 3.2.0. Is there any way to have Dynamo run the specific version. Not the end of the world if it can’t. Our projects are slowly being moved to Revit 2025

5

The python engine being used is stored in the python node being executed. You would have to save two separate versions of the graph, one with each python engine selected for each of the nodes.

6

Thanks. That’s what I figured. The users will all just have to accept that we’re moving to 2025

7

I was about to quit on this effort of transferring data from Excel into a key schedule in Revit. Until I found (in Dynamo’s side bar) that there was an “x” mark about a version of Python that needed to be updated. It was probably due to the Archi-lab ’s “"Key Schedule” node that I was using? After installing the recommended version of Python (DynamoIronPython 2.4.0) the script started to work.
It is not necessary that the data in Excel has headers for “Key Name” and “Comments”, actually that messes up the result.
I hope this helps somebody else, so that they don’t spend as much time as I did trying to make this work.

Transfer data from Excel to a Key Schedule_2025-09-16_01-34-09
Transfer data from Excel to a Key Schedule_2025-09-16_01-34-091662Ă—810 90.8 KB

8

FYI: IronPython 2.7 is a major security risk at this point. I do not recommend its use going forward. It likely will not work at all in Revit 2027 (which is only a half year away).

Look to transition to the OpenXML based excel interop nodes instead.

1 Like
9

Thanks. I did not install 2.7
How do I go about transitioning to the other types of nodes that you mention?

10

Instead of Data.ImportExcel swap for the OpenXML version with a similar name.

For the keynote schedule you’ll need to open the node and swap the Python engine to CPython3 or IronPython3. Avoid anything Python2.

1 Like
11

Curious to know if at some point the ip2.7 package will be removed in line with the recommendation. Totally appreciate it would sledge the package/user base hard but feels like we’re going to land there in 2027 anyway.

12

that node have 2 python script inside, written in 2.7 if i remember, you can just switch to cpython 3 and should work, without error

13
  • Thank you all for the advice. I will look at that node again.
  • It would be good if the authors of Dynamo included a warning about high risk of a version in the Dynamo program itself, instead of an install button to install 2.4 if it is not present, like I saw in this case of the key schedule.
14

The package manager includes such a statement when you go to download the package - in fact it does this for every package which use Python or C# code.