Attribute Rule Import Fails (FGDB, Pro 3.5.2)

[Remmert]

Since updating to ArcPro 3.5.2 we've lost the ability to import existing stored Attribute Rule files to a newly created FGDB. We can copy/paste the same set of rules from FGDB to FGDB. We can apply the same rules as new rules, from scratch, to a FGDB. Those same freshly created rules can be exported without complaint, but cannot be "resused" by importing anywhere else. The rules are not complex, even simple rules like Check Geometry fail to import reliably. Is anyone else experiencing this issue?

[CodyPatterson]

Hey @Remmert 

Just to be sure, you're using this geoprocessing tool? 

https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/import-attribute-rules.htm

Cody

[Remmert]

Yes and we've tried starting from the Geoprocessing Pane as well as invoking from the "Import Rules" button in the Attribute Rules ribbon. Same results. The file geodatabase itself has all the required housekeeping items like GUID and Editor Tracking set. None of the schema or rules themselves have changed in our workflow for quite awhile (Pro 2.5.x?)

[JayCary]

Hi @Remmert,

Can you share the error message you're getting with the Import Attribute Rules GP tool?

[Remmert]

When invoked from the ribbon we just get a prompt "Error Importing Attribute Rule".  Run as a geoprocess in 3.5.2 we get Error 002780 "Attribute Rule Failed to Import" and a row designation. Further down the rabbit  hole, the specific rule(s) that fail to import are any use of "Duplicate Feature" or "Adjacent Vertex Elevation Change", which individually report Error 160712 "Item with same path name already exists." As far as I can tell there is nothing duplicative about either set of rules, we've imported them pre-3.5.2 with no issue. Error 160712 help page only states "this happens so infrequently that no solution exists". Through a variety of testing yesterday we've basically arrived at the assumption that "Duplicate Feature" rules are no longer importable from CSV, at least for our particular configuration.

[JayCary]

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