topic Re: Validation Rule Errors Not Updating When Fixed in ArcGIS Pro Questions

Validation Rule Errors Not Updating When Fixed

jgarcia_qk4 — Wed, 04 Dec 2024 16:16:36 GMT

I have a set of validation attribute rules for a feature class. For example, one validation rule states that the field "COUNTY" must not be null. When I use Error Inspector to validate my rules, all instances of the error are shown. Now the problem is that if I go to my feature class and assign a value in the COUNTY field to all records, save my edits, and hit validate again --- there is no change, all the records which have now been fixed still show up as errors.

If I make a new constraint rule that checks the same thing and repeat, there is no issue. The constraint rule tells me I must have a value for COUNTY and when I assign a value the error goes away. When I use topology rules, the error inspector always updates once the topology errors are fixed. It seems like only validation rules are affected here. Additionally, sometimes the error inspector window fails to show any errors in the table at all, even though at the bottom it will say there are X number of records.

I am using a file geodatabase to store my feature class. Any help here is much appreciated!

Re: Validation Rule Errors Not Updating When Fixed

AustinMartin — Wed, 01 Oct 2025 19:59:22 GMT

Same issue here; using a File Geodatabase with ArcGIS Pro 3.4. I tried using an update cursor to force the update and it appears to work when reviewing the geoprocessing messages but the Error Inspector still shows the errors as if I had not corrected any of the affected values.

Re: Validation Rule Errors Not Updating When Fixed

AustinMartin — Fri, 03 Oct 2025 16:06:09 GMT

UPDATE: Removal of the attribute rules and re-addition (export rules --> import rules from csv) resolved the issue; at least temporarily. Have not confirmed long-term effects.

Re: Validation Rule Errors Not Updating When Fixed

jgarcia_qk4 — Thu, 02 Apr 2026 20:51:50 GMT

@AustinMartin I came back to this problem today, here is what I did to solve my problem. Before, all my validation rules were simple default validation rules that were created by simply clicking "Add Rule" and whose characteristics were determined entirely by an arcade expression. I replaced all of those rules with "Ready to Use Rules, in my case mostly "Query Attributes". It was a bit of a tedious process, but by translating all my arcade expressions through the "Query Attributes" dialog box (mostly by long SQL expressions) I was able to create a set of attribute rules that behave as intended. I hope this helps.