Hi Pro Team,
I found some interesting behavior when trying to batch edit Subtypes through the attribute pane. When updating the Subtype and clicking "No" in the default attributes popup. The attributes for the other field turn to NULL.
In comparison, when updating the Subtype attributes via the attribute table, this behavior doesn't happen.
Below is a recording of the behaviors compared, we're currently using 3.5.2:
Thank you,
Amanda Huber
Hi Amanda,
Are you working with data coming from a local FGDB or hosted feature service in this case?
Thanks,
Rob
@Amanda__Huber We have seen similar behavior when non-nullable fields are used with subtypes. I'm not sure if unchecking the option to 'Warn on subtype change' would help to avoid it in your case or not. I suggest contacting Esri Support to have bug submitted.