When package 2025.10.3 is installed i get this error For Sheets.
You need to uninstall and Reinstall the package from the package manager. The APIs used are version specific, but @john_pierson has done some magic to make sure you get the right one. As such donât install an old build based on the workspace references, just install the latest.
this is the way
And for those who might find this thread and wonder why it is this way, feel free to check out these incredibly amazing films below:
The node was called âsheetsâ? What did it do? My guess itâs that itâs been removed in favor of an out of the box node.
It collect the sheets from Revit this one from Rhythm has number and name the ootb only the name.
Restart Revit, launch Dynamo, open a new graph, and post your Dynamo log file here.
NEvermind - I found it.
FYI @john_pierson - looks like the version of Rhythm I installed yesterday has a 32 bit element ID issue.
@EzDoesIt youâll have to wait for a fix from John to get this version working again, but you should see it in the library as per my screenshot.
ok
Hasnt the sheets node been depreciated from Rhythm or on the list to be? Future Deprecation List ¡ Issue #24 ¡ johnpierson/RhythmForDynamo
Therefore if it will be depreciated you probably want to start looking at alternatives for your script in the later versions of revit. Though if you want the sheet name and number from what you have selected on the drop down you can do this natively in revit 2026 version of dynamo
Or you can do the following to do a search for a specific drawing number to isolate that element only(this was done in revit 2025):
Hi Brendan,
It is an input node so the user can select the wanted sheet.
With number and name is easier to know which sheet to select.
Ah ok. Mustâve missed that node.
You are correct @Brendan_Cassidy , the sheets node has an OOTB replacement nowadays called âSheetsâ.
it is a dropdown and can be used as input as well.
I really do suggest to use the OOTB variant, but this is patched in the latest release if you reinstall Rhythm through the Package manager. I did mark the node as deprecated so it is not findable in the library anymore, but an upgraded graph should resolve with the node.
Note: you need to restart Dynamo after installation for the UI nodes to resolve.
i am gonna use the OOTB node
Ez, the OOTB Sheets node is useless for any project with more than a few sheets, because it only show the name of the sheet which is not unique.
For medium to large projects I get several groups of same name sheets listed and it is impossible to select the wanted sheet from the list.
Hopefully Rhythm package will restore the Sheets NodeâŚ
Thank you John,
But you are saying the Sheets node is still not on the list of available Rhythm nodes?
But at least now if we open an existing graph with that node, it will be able to resolve it�
Honestly, I think itâs all good to deprecate it, since that node was mostly useful to quickly grab a sheet and test stuff in dynamo.
Even as an input in Player, I mean, what graph works or needs only one single sheet?
Still, it would have worked fine and be a nice addition if available
What is seriously perplexing is someone from Autodesk creating a âSheetsâ node that lists only the names of the sheets, and thinking that was of any use.
Obviously the person had no clue what people do with Revit and Sheet sets.
This is also understandable: i shouldnât expect a programmer or software engineer to know what designers / architects do.
However, I am expecting product designers and UX designers and the whole team behind Revit and Dynamo feature request and roadmap site, to know.
Anyways, thank you again, John, for you effort and the time you spent for the community.
Great work as usual.
Considering youâre like the third person to ask about this in 5 years that the node in question has existed, perhaps this is a case of âwhat I need doesnât reflect the needs of most usersâ? I canât recall ever seeing duplicate sheet names in a single model I worked in, so that would have been fine by me. Perhaps revisiting your naming standard is in order as that will have benefits beyond the Dynamo node (think of an intern opening one of your models looking for the âfirst floor planâ or some other sheet with duplicate names).
Either way the Dynamo team will try to get this into the backlog for the Revit team (they own Dynamo for Revit), and those of us inside the factory will advocate for the update as well. Doesnât make it a sure thing though, as I am positive someone will advocate of another alternative (cue someone saying it should follow iso19650 standard not ânumber and nameâ or ânameâ).
I hear you Jacob,
but this is the first page of what the OOTB node looks like on a medium sheet file (less than 200 sheets project) in my office:
When you create several options in the same project file (not to mention with multiple sheet sets / collections), it is unavoidable to get sheets with the same names.
Revit allows non-unique sheet names, and also, ISO19650 (which we use) does not really dictate a sheet naming convention, but rather sheet and PDF sheets numbering.
Regardless, if a single man operation like Johnâs thought it was a good feature to list sheets by sheet number and name, then one would expect a large corporation to also be thorough when designing its products.