ArcGIS Pro 3.0.1: A record in the reviewer results session table disappears as it’s updated when working with data reviewer,

[JamalNUMAN]

ArcGIS Pro 3.0.1: A record in the reviewer results session table disappears as it’s updated when working with data reviewer,

In the screenshots below, the record of feature #210 disappears as it’s updated and marked as “resolved”.

What could be the issue here?

My understanding is the record should be kept in the table in all its life cycle: review, correction, and verification status

[JayCary]

Is the error result actually still in the database or is the error result being moved out of the current view due to the sort currently applied to the pane?

[JamalNUMAN]

The issue can be reproduced as follows:

• Select a feature and commit it with “delete feature” as “error type”
• As the record of this error appears in the review results session table, zoom to it
• Select the feature that has the error and delete it
• Go back to the record that represent this error review results session table and update it
• Once the “apply” is clicked in the “update result” pane, then the record disappears

The screenshots below shows the steps above

[JayCary]

Thanks-much for the clarification!

I would suggest turning-off your error layers to ensure that you are not accidentally deleting the error feature during your edit.

[JamalNUMAN]

Does deleting the feature that has an error gets its record deleted from the reviewer result table?

All what I do is deleting the feature that has an error and then its error gets deleted when performing the update

[JamalNUMAN]

Attached is a video that demonstrates the issue I’m struggling with

[JayCary · Accepted solution]

Thanks for sharing your workflow!

The development team has reproduced this behavior in ArcGIS Pro 3.0.1 and it appears to affect project configurations where Reviewer results are co-located with the data actively being edited. To avoid this issue, please use a separate geodatabase to store your Reviewer results.

The team has logged an internal bug for this issue and it will be fixed in the next release of ArcGIS Pro.

If needed, please contact technical support to start an incident to document this issue. This will enable you to track the progress of this incident.

[JamalNUMAN]

Great. It works like a charm

Enabling the “reviewer results” in a geodatabase different from the one that accommodates the feature classes being handled resolves the issue. This workflow is more appropriate and makes sense.

Thank you for the prompt help