Select to view content in your preferred language

Marking Exceptions

687
4
01-27-2025 01:48 PM
Remmert
Occasional Contributor

Working in Pro 3.4, I have a collection of Attribute Rule Validations. Some, when I "Mark Exception" also automatically update "Error status", "Error phase" & "Correction notes". But there is a set of rules that only "Is exceptions" updates. The only difference I can see between the validations is that the non-updating ones are Severity 5. Whereas the rules that auto-update error status are Severity 1. 

Any idea why the error lifecycle information doesnt update?

T_Remmert_0-1738014437465.png

 


Rev. Remmert
ESRI Gold Partner
0 Kudos
4 Replies
JayCary
Esri Contributor

Hi,

It sounds like you have a mix of error features created using both Arcade and Data Reviewer.

Data Reviewer-generated errors are managed differently than those created using Arcade. Here is a topic which outlines the lifecycle workflow for errors created using Data Reviewer's automated checks or visual QC tools.

You can quickly identify this difference by adding the Phase and Status columns to the Error Inspector pane by enabling the Show Status option (found in the the menu button menu.png).

0 Kudos
Remmert
Occasional Contributor

All of the rules I cited above are "Ready to Use Rules" executed as Attribute Rule validations (Feature on Feature). I have discovered that the errors that don't automatically advance phase/status when flagged as exceptions are "composite" rules. So I feel better knowing there's some commonality/sanity to the behavior.


Rev. Remmert
ESRI Gold Partner
0 Kudos
JayCary
Esri Contributor

Thanks-much for the clarification (and heads-up)!

I was able to reproduce this behavior using ArcGIS Pro 3.4 and ArcGIS Enterprise 11.4 with error features created using the Composite check. The development team has logged an internal bug to address the issue.

I would suggest starting a technical support case (and log a bug) if you'd like to track progress and be notified when the issue is addressed.

Thanks again for the feedback!

0 Kudos
JayCary
Esri Contributor

Just a quick note that this issue has been addressed in the upcoming ArcGIS Pro 3.5 and ArcGIS Enterprise 11.5 releases. The team is also planning to include this fix in future ArcGIS Pro and Enterprise patches.

Thanks again for sharing your feedback!

0 Kudos