Hi,
I ran into what I am thinking might be a bug and wanted to get the group's input before I went to support.
We just converted to PF from many AutoCAD dwgs and in our first week working with the live data. We are running Pro 3.3.5 and Enterprise 11.3. We are currently knee deep in the cleanup of ~240k (180k are the cogo on the parcel lines) errors that came out of the conversion.
Looking at the data type for the Records feature class, the Name field allows a NULL entry.
This sets up the possibility of entering nothing when creating a new editing Record name with a value of Null and a number, that is not the Record Name, is placed in the active record display suggesting some sort of validity. The down side of doing this is that if you attempt to use the Recently Used Records no value will be displayed and will most likely unstabilize or crash Pro.
Yes, the documentation and training all says to put in a value which is good practice but how do we best manage the accidental bad input that does not appear to be handled?
Regards,
Tom
Hi - I would look into attribute rules to catch this - perhaps a constraint type attribute rule?
Thanks much for the suggestion!
I will give that a try during our next planned service update in July.