I have a relationship class between a parent feature class and a related table, where I want to ensure there is at least one corresponding related record present for each origin value found in the parent feature class.
I've created an attribute validation rule on the parent feature class using the "Ready to use" Validation Rule called "Relationship" in ArcGIS Pro 2.9. and enabled the search goal "Origin unreferenced or null key value" on the attribute rule. When using the error inspector in ArcGIS Pro, the rule correctly flags a feature as missing a related record the first time validation is run. However, if a related record is then generated, and validation is re-run the error persists! The error only seems to resolve if the feature itself is also edited in some way.
Seems like this "Ready to use" validation rule has limited utility if its error persists until the parent itself is edited. If there is a workaround for this (other than directly editing the parent feature in some way), I would greatly appreciate it.