nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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?

Find more posts tagged with

Accepted answers

All comments

JayCary

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!

Remmert

The issue has not been resolved. v3.5 through 3.6.1. I have also narrowed it down to importing validation rules that use "Duplicate Features" (when attributes to ignore are enabled) and with "Query attributes".

My solution was to replace Duplicate Feature checks with Feature on Feature checks. I am also able to copy/paste the wayward rules from an existing functional pre-3.5 FGDB.

rsagardia

We are experiencing similar behavior. For FGDB rules can be created from scratch and work as intended, but some rules fail on import when trying to restore from a CSV.

We observed issues importing validation rules that use "Duplicate Features" (when attributes to ignore are enabled) and with "Query attributes".

Currently we are using ArcGIS Pro 3.6.1

VanessaSimps

Have there been any resolutions with this? I am having the same issue.

AparnaSunki

Hi ,

We also encountered same issue. We were able to manually add rules and copy paste rule from other FGDB however when we import , import fails. In fact same issue prompted if we export manually created rule in 3.5.2 , export the rule and try to import same rule again. Any resolution

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.

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

Hi @Remmert,

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

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

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

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.