Latest Contributions by JayCary

Hi, That's very weird. I would check whether your ArcMap Geometry on Geometry check is referencing data in two different geodatabases. For example, data source listed in the Feature Class 1 parameter is in a different geodatabase than the data source list in the Feature Class 2 parameter. If so, then you will need to move these data sources to be within the same geodatabase. Attribute rules do not support mixing data sources from different geodatabases. If this isn't the issue, then I'd suggest starting a case with technical support to see what's going on. ... View more

I'll leave this idea open in the event that other folks have scenarios that would require an OR condition. ... View more

Hi, Here are a couple of suggestions to try when migrating Reviewer Batch Jobs to attribute rules: At Pro 2.5, the Feature on Feature check (formerly known as Geometry on Geometry) was released and it does support the comparison on attribute values (Attribute Relationship parameter) for those features that match a specified spatial relationship. In attribute rule workflows, a requirement of this check is that the data source used in the Features to Compare parameter (EMS_Districts in your example) must include a GlobalID field. At Pro 3.0, the Export to Attribute Rules command was released to enable the export of checks stored in a Reviewer Batch Job to an attribute rule .csv. You can see a demonstration and best practices when using this workflow in the Migrating Quality Control Workflows to ArcGIS Pro technical workshop (at 06:11).   ... View more

Would someone be willing to share a configuration of the Duplicate Feature check (with source and destination schema) that we (or Esri technical support) can test? I've tried various combinations of export/import based on the latest feedback and cannot reproduce. Thanks in advance for the feedback! ... View more

ArcGIS Data Reviewer's Nonlinear Segment check (used from the Run Data Check command) might be an option here to bulk identify features that contain curves. ... View more

Hi, The ability to evaluate only changed features in a named version is already available! This option can be found in the following workflows: Error Inspector (ArcGIS Pro) Evaluate operation (REST) Are there other workflows that are missing this option? ... View more

Closing due to the upcoming deprecation of Reviewer Workspace and related tools. Learn more about the deprecation. ... View more

@Remmert Thanks for the details. A couple of details to verify when importing these types of Reviewer checks into a new geodatabase: Duplicate Feature Verify that the dataset specified in the Features to Compare parameter has a globalID assigned. Verify that the dataset specified in the Features to Compare parameter exists in the geodatabase (and has the same geometry and datum as the input feature class) If using subtype/attribute filters, verify that those subtypes and/or attributes exist in the input feature class. This would also apply if an attribute filter is applied to the dataset specified in the Features to Compare  parameter.   Adjacent Vertex Elevation Change Verify that a vertical coordinate system is defined for the input feature class If using subtype/attribute filters, verify that those subtypes and/or attributes exist in the input feature class. If these are covered, I would suggest a call with technical support to see if they can reproduce the error. ... View more

Hi @Remmert, Can you share the error message you're getting with the Import Attribute Rules GP tool? ... View more