All ArcGIS Pro Users:
In order to edit in the Parcel Fabric, Editor Tracking must be enabled. Editor Tracking, as managed by the software, will, of course, update the Last_Edited_Date & Last_Edited_User fields in each feature class of the Parcel Fabric, triggered by any geometry or attribute update event. Alongside this, we also employ several Attribute Rule Validation Rules for both our Parcel_Poly & Subdivision_Poly feature classes, evaluated on demand using the Error Layers and the Error Inspector. In order to accommodate the potential use of Validation Rules, each feature class in the Parcel Fabric has a ValidationStatus field already in its schema. The issue arises when the Validation Rules are run, since all features in the map extent are evaluated, updating the ValidationStatus field accordingly – and since the calculation of this field constitutes an update trigger where Editor Tracking is concerned, all of the aforesaid features also received an updated Last_Edited_Date & Last_Edited_User fields – which totally renders those fields useless in terms of tracking actual parcel edits, as eventually, over time, nearly every parcel in the jurisdiction will have a misleadingly recent edit date.
Has anyone encountered this issue where the Attribute Rule causes the Editor Tracking capability to update fields in records not intended to be updated due to map extent selecting records to be updated?
Any feedback related to this topic is greatly appreciated as it seems like a deficiency of the ArcGIS Pro software.
