I was just trying to work out adding some data to a parcel’s UDP, but when wiring up a test graph, I realized there seems to be an error with the node:
Which I know is incorrect, since I have already assigned a bunch of data to all my parcels:
Has anyone else run into this or is this just a ‘me’ issue?
Hi @AdammReilly,
I just gave it a quick test and wasn’t able to reproduce.
If you’re able to share your DWG, I can take a closer look.
Sure, here’s the file I’m working with.
Drainage Area Map.dwg (1.1 MB)
The issue is that there are several properties in Unclassified that are null/undefined. We can add a check to handle this case, but I’m curious how these got here?
@zachri.jensen
I was just writing the same observation.
Those are all Area label expressions and I’m not sure why they’d be listed in the UDP.
Got it, thanks. We’ll get it worked out.
I need to write back to the UDP and I don’t see any nodes for that, so I’ll probably create a few custom ones for that and address this error checking until y’all get a fix in place 
Thanks for the help!
1 Like
Just wanted to provide an update on editing UDP 
I created these two nodes:
The GetUserDefinedProperties node catches the error related to expressions being lumped in with the Unclassified dictionary.
The SetUserDefinedProperty takes the classification dictionary name, the property name and the value. I played with taking it as a dictionary of name/value, but I felt it was too cumbersome to force a user to build a dictionary just to internally break it apart again. I’m going to rename the inputs to be more clear, but this works really well so far.
1 Like