Today I experienced an error when trying to create Property Set Definitions with Dynamo. I can’t test it in Civil 3D 2025.1 (the Update 2 can’t be uninstalled) or earlier.
Creating a Property Set Definition with 3 Property Definitions in Dynamo, the result says that it created the Property Definitions:
But when reading the PDs from the PS, it shows an empty list:
When reading the PS in the drawing with the PROPERTYSETDEFINE command, I see the Property Set Definition in the sidebar but it is empty. As soon as I click on the name, a Fatal Error occurs.
Can anyone confirm it is not possible to create a Property Set Definition with Dynamo or did someone succeed in some way?
Seems like I recently ran into similar case.
Firstly - @Anton_Huizinga I reproduced your script and got same behavior (Empty List in Dynamo and Fatal error in Civil3D UI).
I did a workaround that way I firstly created empty Property Set and if this was in drawing I added manual PropertySetDefinitions.
Thanks for testing! It must be a bug if you see the same behavior.
Your workaround is not working for me, at least it is not possible to create and add in the same script.
Now I remember, when I was coding the Object Data nodes in The Civil Nodes package, to create the Object Data table I had to apply a drawing lock, which is unusual for Dynamo. Maybe because Object Data is just like Property Sets not really part of the Civil Document? @zachri.jensen: can that be the case here too? I assume you can have a look at code level for these nodes 
Yes - I wasn’t also able to create and add in same script. So I added empty PS in drawing and after that I launched Dynamo and run the script which is shown above.
1 Like
I think there is no other workaround at the moment. The Property Set Definition created with Dynamo, is corrupt and will be like that, even after restarting Civil 3D. As soon as you click on the PSD in the dialog, a Fatal Error occurs. AUDIT or RECOVER does not find any issues to fix.
2 Likes
Hi @Anton_Huizinga and @markus.toon,
Thank you for flagging the issue with manual property definitions. We fixed a defect with this node in 2025.2 (see release notes), but it seems that a regression was introduced. We’re still investigating and I will keep you updated.
1 Like
After further review, the issue is isolated to creating manual property definitions with the data type set to True/False. All other data types should not be affected. And it actually was an issue in Civil 3D 2025.1 as well and went undetected until Anton caught it.
Thanks again for bringing this to our attention! We will get it fixed.
4 Likes
Wow! Good find! Without the True/False Property Definition, it works as expected.
Good to know
2 Likes
There is an issue with the Integer and the List Property as well. You can add them to the set, but the List Default value can’t be set and the Integer Default value is a weird number.
Adding a Property Set to an object results in a message:
And in the end only the String Property is accessible.
Thanks. We also discovered the issue with the default values and have corrected it.
2 Likes
@Anton_Huizinga if you have time, can you download the latest Civil 3D 2026 beta and verify that these are working how you expect now?
