BUG-000174960 for ArcGIS Pro

Bug ID Number	BUG-000174960
Submitted	March 12, 2025
Last Modified	June 24, 2025
Applies to	ArcGIS Pro
Version found	3.4.2
Operating System	N/A
Operating System Version	N/A
Status	As Designed

Additional Information

This is by design. In 2.9.13/3.x we fixed a bug with relationships and attribute rules where the rules were not triggering. That is why it "worked" in 2.9.3 because the rule was never triggering. Now with the fix, the Add new to relationship translates to two edits -> create a new row on the destination -> update the row to set the foreign key (this didn't happen before which was not correct) the second update doesn't have field value populated which causes the attribute rule to fail. To fix this you have can allow the update to happen if the foreign key is being updated by changing the rule as follows //prevent the edit only when the user makes an update, not when the foreign key gets updated if ( $feature.field == null && ($originalFeature.foreignkey == $feature.foreignkey) ) return false; //else allow the edit return true; alternatively you can set a default value for "field"

Workaround

Open the attribute table of the feature class, select a row or feature and click the Menu button (three lines) in the upper-right corner. Navigate to Related Data, select the related table and add rows directly.