Inconsistent Execution of Attribute Rules

Question

Hello all.

I have an Attribute Rule in place on the items within a feature dataset (ArcGIS Pro 3.2 and Enterprise 11.2) that is executing inconsistently. It is designed to grab the nearest road segment from another feature class in the feature dataset and populate a field with relevant information upon Inserting a record.

The rule was designed and tested with no errors in a test environment and then replicated in our production environment. The rule worked fine to start and is now throwing error messages within Field Maps when trying to submit new records. When replicating the creation/insert process in both the Enterprise Portal Web Map through a web browser or within ArcGIS Pro using a direct database connection, there are no error messages thrown when submitting a record.

Any ideas as to what may be causing this issue?

drWood · Answer

Hello,

We never found a solution and had to scrap use of the attribute rule for the time being and revert to a manual population during in-office QC workflows on our new field data collections.

GerbenWolf · Answer

Hi,

Did you already found a solution? I have a very similar situation and problem as you describe.

In my case I work with Enterprise 11.2 and ArcGIS Pro 3.4.2. The Attribute Rule is designed to return the name of the (sub)project area from another feature class in the feature dataset and populate a field with relevant information upon Inserting a record. In so, I check the number of intersected area's and return the name of the area when the count equals 1. However, I get an error message that it encounters an unexpected null value while returning. So this implies a certain contradiction. In addition, null values are allowed.

drWood · Answer

@CodyPatterson, The fields are not set to required for any of them so there's no constraints being implemented there. The issue is still persisting in Field Maps, but creation of new records works without a hitch in both the web map via the REST service and in ArcGIS Pro using a direct connection to the enterprise geodatabase.

However, when I try to create a record using the REST service in ArcGIS Pro I am met with the same error shown in Field Maps.