Need some help converting old Geometry on Geometry checks

[TerriWaddell1]

Hello,

I'm trying to convert our old Desktop-based Data Reviewer batch jobs to the newer attribute rules (mostly as validation rules so far).  I have numerous checks on various feature classes that used the older Geometry on Geometry check to basically make sure a field in one feature class matched the thing it is sitting on in another feature class. They used the "Compare Attributes" setting that was in Geometry on Geometry checks.

Example:

ESN feature class has an EMS field which lists the EMS that is responding if a call comes into that ESN. (Yes, still using ESNs, don't get me started...)

My old check looks at the EMS field's value in the ESN feature class and makes sure it matches the EMS field's value in the EMS polygon it's sitting on in the EMS feature class.

I cannot for the life of me figure out how to update these kind of checks to the newer Pro/Data Reviewer attribute rule checks.  They don't import, and trying to do them from scratch has me stumped.  Feature on Feature doesn't let me compare attributes like the old Geometry on Geometry checks did - that's missing as far as I can tell.  I realize I can do something like a spatail join and then compare features, but it was so much faster/easier when I could do this in Data Reviewer's Geometry on Geometry check that I hate to go backwards. 

Does anybody know of another way to do these in the more modern checks, or am I going to have to go back to doing the old spatial join method and then compare attributes there?

Thanks!

More details from my original Geometry on Geometry check in case it's useful:

ESN feature class is named ESN_Boundaries and was set as Feature Class 1.

EMS feature class is named EMS_Districts and was set as Feature Class 2.

Spatial Relation Check was "within".

Compare attributes was used, and it was set as follows:

Data Source 1 ESN Boundaries attribute EMS <> Data Source 2 EMS_Districts attribute District.  

Error condtion was EMS <> District

[JayCary]

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).

[TerriWaddell1]

I haven't had issues exporting to RBJ to CSV.  The problem is this particualar type of rule won't import. 

I'm trying to compare fields from two different feature classes based on their spatial location. The Feature on Feature check seems to only allow you to check things in the same feature class.  I've tried creating the check from scratch but there is nowhere to list/add the second feature class.  

It's looking like this functionality is simply gone in Pro's attribute rules, can you confirm or am I missing something?

[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.