I’m developing a Dynamo graph that will read and modify our Sheetset. We are using the AMR sheetset nodes for this graph but it’s not accessing drawings below the second level. The drawing circled in the attached photo doesn’t get read or written when executing the graph. We are using SheetSet.Subsets but that only allows access to the first level. Is there a way to reach all levels of the sheet set?
Not sure what the AMR Sheetset nodes are. But what are you trying to accomplish with the script?
AMR Sheetset is a package for managing sheet sets in Civil 3D where often 100’s if not 1000’s of individual DWG files have to be coordinated into a coherent collection for issuing the deliverables.
Yes, I am glad we have Revit for the buildings side of AEC, why do you ask?
1 Like
There are two graphs that I’m working on, one that will read data from the sheet set manager and export to Excel, and the other will write data from Excel to the sheet set manager.
This will allow us to populate the data in the sheet set manager for the full sheet set and for individual sheets from Excel, rather than the manual task of populating each sheet. Our title block’s attributes are linked to the sheet set, so we can easily update our title block’s fields.
The issue I’m having is that the nodes I’m using don’t look lower than one level in the sheet set manager, so the drawing I have circled isn’t read from or written to.
The package is still missing a Subset.Subset node.
It’s on my list to get to but haven’t quite gotten there yet.
1 Like
Thanks for the update @AdammReilly. Do you have a timeline when you want to get there, or is it just something you will get to later?
I’ve got several projects that are taking precedence over this right now. The main hold-up on new updates to this is that I want to really dig into finding a way to publish the package in such a way that all the civil 3d version builds could use the same package/version. Right now, once I build it for one C3D release, I can’t build and publish it for the prior release and I don’t like not being able to provide some backwards compatibility for the package.
Hey Adam! Quick question, how are people doing this now? I feel like this must have come up in the past and there’s a workaround people use?
Right now, I’m loading in the specific release of Autocad’s SSM API, then building a new dynamo package. when the package manager consumes it, I am versioning it to match the autocad version and stepping the minor version (ie, 2025.35) Because that major version is tied to the software version, the package data stores that version but because I went with doing it like that, the package manger won’t let me do an update to 2024.X because it sees the 2025.x as newer. So, once I do a 2026.x release, all the prior versions are unable to be updated.
Someone told me, at AU, there’s a new mechanism for multi version updates, or something like that, but I haven’t had the time to look into or for this yet.
Hello, thanks for the reply! So, how are people doing this now? Python? Any other nodes from other packages you can use? Just wondering what options there are and what others have done in the past to overcome this.