Orphan Errors - can I delete them?

[DrewDowling]

We have a number of errors in the error tables on features that no longer exist in the database. I think that, rather than fix the validation error, editors deleted the features and created new ones from scratch. This has left a number of errors in the error tables that are not related to any actual feature. The features still exist in the table but are marked as deleted so they don't show up in sde.default.

I tried deleting the error row directly from the table in Pro but got an error message that deletes are not permitted.

"Error: Layer Validation Polygon Errors does support delete operation"

How do I remove these errors that refrence feature that no longer exist?

[HusseinNasser2 · Accepted solution]

Hey Drew, that should technically not happen. and if it does it is probably a bug,

When you delete the source feature, we also delete all errors associated with this feature. Is it possible that the delete happened outside of software (like in SQL? )

Would be good if you have a repro case for how errors are orphaned. 

[DrewDowling]

I didn't do the delete myself but I don't think SQL would have been used. I'll follow up with the analyst who did it.

I will say that it is not the only feature class where this has happened. There are 2 others displaying the behavior.

All of them are part of a parcel fabric so maybe it is related to that. I will do some more testing to see if I can recreate it.

That said, is there a way to fix it? Preferable without having to unversion data. If I delete the validation rule altogether will the related error features get deleted as well?

[HusseinNasser2]

not pretty, but you can delete the rule that the error points to and that should delete all the error features, you can simply just recreate the rule again. Careful that this also deletes all error features not just orphaned ones. 

I think disable/enable also does the same thing (I might be wrong)