laptop and a wrench

Bug

Adding values to more than one attribute to a related table through a calculation attribute rule results in an error: "Edit operation failed. The attribute rule returned a value, but no field was specified in the rule".

ArcGIS Pro
Bug ID Number BUG-000174676
SubmittedFebruary 28, 2025
Last ModifiedMarch 24, 2025
Applies toArcGIS Pro
Version found3.2.1
Operating SystemWindows Server
Operating System Version2016 64 Bit
StatusAs Designed

Additional Information

This is the intended design, but the rule is written incorrectly. A literal value cannot be returned if no field is assigned. Currently, the rule is not assigned to any field. However, there is an else statement that may execute and return a value of 101. If that branch is executed, 101 is returned without a designated field to store it. var gID = $feature.Foreign_Key var related_Features = Filter(FeatureSetByName($datastore, 'cities', ["CITY_FIPS", "STATE_CITY"]), 'GlobalID = @gID') var test = First(related_Features) if (!IsEmpty(test)){ return { "result" : {"attributes" : {"XY" : test.CITY_FIPS, "STATE_CITY" : test.POP1990}} } } else { return 101 } The user need to specify which field to return the 101 to or simply if they don't want to do anything replace it with return; var gID = $feature.Foreign_Key var related_Features = Filter(FeatureSetByName($datastore, 'cities', ["CITY_FIPS", "STATE_CITY"]), 'GlobalID = @gID') var test = First(related_Features) if (!IsEmpty(test)){ return { "result" : {"attributes" : {"XY" : test.CITY_FIPS, "STATE_CITY" : test.POP1990}} } } else { return; }

Workaround

As a workaround, create multiple rules for one table, where each rule will dedicatedly calculate the values for one field.

Steps to Reproduce

Bug ID: BUG-000174676

Software:

  • ArcGIS Pro

Get notified when the status of a bug changes

Download the Esri Support App

Discover more on this topic

Get help from ArcGIS experts

Contact technical support

Download the Esri Support App

Go to download options