As described in this question:
Can a calculation rule update a record in the same feature class, same field, as the edited record?
For example, if a user edits the common_name for OID1, I want the attribute rule to additionally update the common_name for OID 2. Is this possible?
OID custom_id common_name 1 "Group A" "Name A" 2 "Group A" "Name A" 3 "Group B" "Name B" 4 "Group B" "Name B"
Could functionality be added to attribute rules that would let us update a different feature in the same FC as the edited feature?
(This is not to be confused with making an update to a domain description. We don't always have domains on fields that have common values.)
If this functionality already exists, then maybe the idea should be changed to:
"Prevent infinite loops when attribute rule edits same feature class"
From @JohannesLindner in Can a calculation rule update a record in the same feature class, same field, as the edited record?:
You just have to take precautions against infinite loops (feature 1 updates f2, which in turn updates f1, which then updates f2, etc).
I have figured out a workaround to this by simply setting the values to look for the first record that matches the filter criteria set and then set all records that get updated to the attributes of the first returned record. This nullifies the cyclical update issue as I have come to find out.
Yes it is possible to update the same class with attribute rules and prevent infinite loops, I authored a post detailing this with an example.
Prevent Infinite loops in Attribute Rules
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.