I’m having an issue using the Data-Shapes package in Dynamo.
When I run a graph that contains UI.MultipleInputForm++, no dialog window appears. The node returns null values and nothing is shown on screen.
If so, double click on one of the simpler nodes like ‘number input’ to edit it, then make sure you have the required Python engine installed for the package.
If not, install it.
Of so, copy the Python node, switch back to the workspace, and past the Python node there. Wire in inputs to see if the nodes run there; if so, check another node until you find the error.
It is been a while since I used DataShapes, but I do remember that the toggle expects a boolean. Could you try a boolean node with True, or a code block with True;
What I understand from that spanish message is that the package is already installed and can’t be installed again .
“System.Reflection.Emit.TypeBuilder" this indicates that you are likely in an older version than Revit 2025. Can you confirm ? If so , best course of action is to downgrade to version of Data-Shapes 2025-3-120 , and install the DynamoIronpython2.7 package version 2.5.
I’ll weigh in here too… the BEST option for older Revit 2025 releases will be to either prevent any and all external data from getting onto the system, or updating Revit to the latest build. That particular hotfix (2025.4.4) includes a patch to address a common vulnerability exploit (CVE - meaning there is a security issue shown online) that scores high (between 7 and 9 out of 10 as it allows an attacker to execute any code they’d like on your CPU) by just opening or loading a maliciously crafted family. More info here: Security Advisories | Autodesk | adsk-sa-2025-0021
The second best option would be to install the older versions.
Unfortunately, the CPython3/PythonNet2 engine in Revit 2024 has some additional bugs,
This is probably to related to the build/compilation of PythonNet 2.5.2 (Python.Runtime) with Net.Standard 2.0 as target
It was fixed with Dynamo3+ (CPython3/PythonNet2 or better …PythonNet3)
Thank you all for the information and suggestions. You were right — after installing the 2026 version, the issue was resolved and everything worked without any problems.
