Revit 2025 and DataShapes General Inquiry - Appears not to work the same as in 2024 and prior

Hello!
I just installed Revit 2025 and am testing my scripts before giving my team the green light for modeling / data extraction in that version.
The first script I am testing (and many of my other scripts) start with the DataShapes Listview Data node and MultipleInputForm++ to query the model for a list of items to choose from before continuing the script.
When I open the script, everything looks good - no apparent node issues.
I did get an IronPython version error and installed version 2.73.2.0
But when I run the script, it seems like the Datashapes nodes are not interacting with the model - the script skips right past and therefore produces unusable, unfiltered data.
Looked online first and saw that there might be a Datashapes package version specifically for 2025. Are we able to confirm this, and if so, is there a link to it for testing?
Or do I need to find a workaround going forward?
Or could this be another issue that I should check into?

Thank you!

Your IronPython2.7 version seems out of date (not by much though)
Working with current versions of IronPython2.7 (3.2.1) and Data-Shapes (2025.3.119)

Ah, I also hadn’t needed to update the DataShapes in a long time. Doh! I just looked and there are many updates. I updated to the version you mention and everything is fine. That was easy. Thank you!
Now I need to go back and test slightly earlier versions of the package to see if I can just use one script across Revit 2023, 2024 and 2025. Was hoping to only need one set, now that we’re past the R2023 change to Dynamo.
Thanks again!

The recommended best practice is a new package library for each Revit release, as many common packages (i.e. Archi-Lab) require unique builds.

Similarly I recommend a different graph library for each release, working oldest to newest (or vice versa). This reduces the need for custom tooling and quarters the amount of error handling (tasks which I think will continue to grow in difficulty due to .NET changes and Dynamo API changes).

1 Like