ArcGIS Pro 3.0.1: How to sort ascending\descending the fields of the “error inspector” window when working with validation attribute rules?

424
2
Jump to solution
09-12-2022 10:39 AM
JamalNUMAN
Legendary Contributor

ArcGIS Pro 3.0.1: How to sort ascending\descending the fields of the “error inspector” window when working with validation attribute rules?

 

For example, in the screenshot below, I couldn’t figure out how to sort the “error message” field ascending\descending

 

Clip_68.jpg

----------------------------------------
Jamal Numan
Geomolg Geoportal for Spatial Information
Ramallah, West Bank, Palestine
0 Kudos
1 Solution

Accepted Solutions
John_Jones
New Contributor III

Thanks Jamal, this is a known limit in how the error table handles the topology errors being split into 3 separate tables with different geometry types (for point, line and polygon errors).  At present, as these are 3 different tables but otherwise have the same schema (other than the difference in the shape field type), we present the errors all together but sorting involves sorting all three tables and then merging them appropriately.  While this normally isn't too bad we worry about performance / memory problems with large error tables.  More work needs to be done internally to support this (or work arounds to sidestep the underlying issues).  As such we have not yet been able to provide field sorting of this table (although we certainly recognize the usefulness).  Unfortunately this is a case where the implementation is more involved than we would like and thus this work has taken a backseat to other enhancements.  Certainly, as demand drives we will continue to investigate solutions.

View solution in original post

2 Replies
John_Jones
New Contributor III

Thanks Jamal, this is a known limit in how the error table handles the topology errors being split into 3 separate tables with different geometry types (for point, line and polygon errors).  At present, as these are 3 different tables but otherwise have the same schema (other than the difference in the shape field type), we present the errors all together but sorting involves sorting all three tables and then merging them appropriately.  While this normally isn't too bad we worry about performance / memory problems with large error tables.  More work needs to be done internally to support this (or work arounds to sidestep the underlying issues).  As such we have not yet been able to provide field sorting of this table (although we certainly recognize the usefulness).  Unfortunately this is a case where the implementation is more involved than we would like and thus this work has taken a backseat to other enhancements.  Certainly, as demand drives we will continue to investigate solutions.

JamalNUMAN
Legendary Contributor

Thank you for the informative answer.

Best

Jamal

----------------------------------------
Jamal Numan
Geomolg Geoportal for Spatial Information
Ramallah, West Bank, Palestine
0 Kudos