Latest Contributions by JayCary

For the country rule (implemented using the Data Reviewer's Feature on Feature check), you may want check the error feature's phase/status values to determine if the error is fixed (how to enable life cycle phase columns). Error features created using Data Reviewer-based rules follow a different life cycle than those created using Arcade. ... View more

Hi, Another workflow for exporting attribute rules is to use the Export Rules command found in the Attribute Rules view ribbon (doc for reference). One of the benefits of this workflow is that you can verify that the feature class contains rules since the geoprocessing tool does not warn you if the input table contains no rules. That said, upgrading to a later release of ArcGIS Pro should not have an impact on attribute rules that have already been saved in a geodatabase. Are the rules created using ArcGIS Pro 2.6 not visible when opened with a later release of ArcGIS Pro? ... View more

Hi, There are two workflows for implementing validation attribute rules (Arcade and ArcGIS Data Reviewer). Which implementation are you using? ... View more

@AaronCrisanto and others who find this idea, support for adding user-defined messages for exceptions can be found on the latest version of the Data Reviewer product roadmap. In the product roadmap it is referred to as "multi-persona lifecycle management" and is planned to support exceptions and error features created during visual review of data. Feel free to add your specific use-case and kudo this idea to show your support! ... View more

Hi, There are two supported workflows for managing Data Reviewer-based errors in ArcGIS Pro 3.3. These include management of errors created using: Reviewer-based validation attribute rules where errors are managed using the Error Inspector pane. Reviewer Batch Jobs where errors are managed using the Reviewer Results pane. Could you clarify which workflow you are referring to? Thanks! ... View more

@CarsonGThis enhancement to the Browse Features pane is planned for the next release. ... View more

@BethanyHodge and others who find this idea, see the following ArcGIS Pro ideas requesting this functionality and add your specific use-case and kudos to show your support: ArcGIS Pro Topology Error Inspector - Sort Headers ArcGIS Pro Error Inspector - Source Layer Filter Note: The Error Inspector supports error management for multiple workflows including Topology rules and Attribute rules (where Data Reviewer error features live). Enhancements to the Error Inspector are typically shared across these workflows. Thanks! ... View more

Wouldn't the Differences view support the workflow identified above? ... View more

Thanks-much for the feedback. Unfortunately, support for data validation workflows which leverage Reviewer Batch Jobs is planned for deprecation in a future release of ArcGIS Pro. ... View more

This scenario may be supported depending on how attribute values are stored in the participating features. Please feel free to update your idea if the below does not work! The Feature on Feature check can be configured to identify points with attribute values that do not match nearby line features. Using the Esri local government schema, the following configuration of the check identifies Site Address Points that contain Full Road Name (FullName) values that do not match the Full Road Name (FullName) values of nearby Road Centerline features. Feature on Feature check configuration Input feature class: SiteAddressPoints Features to Compare: RoadCenterline Features to Compare Filter (optional): Roadclass includes the value(s) 'Minor Arterial','Major Arterial','Local' Spatial Relationship: Intersects Horizontal Search Distance (may vary): 500 US Feet Attribute Relationship:  FullName is equal to FullName Invert Relationship: True Depending on your schema, a similar configuration may also support evaluation of address numbers against road centerline address ranges.  ... View more