It seems like triggering fields don't recognize updates made by other attribute rules and I'm just curious if others have run into this.
I have 3 attribute rules configured to update street name fields in a road layer. There are two sets of parsed out street name fields, one set for abbreviated street names like E MAIN ST, and one set for fully spelled out street names like East Main Street. There are also full street name fields for each. The configured attribute rules are as follows and are configured to run in this order:
- The user edits the parsed out abbreviated street name fields, and the first attribute rule populates the fully spelled out street name fields accordingly based on the abbreviated values.
- The second attribute rule concatenates/populates the fully spelled out full street name from the parsed fully spelled out street name fields.
- The third attribute rule concatenates/populates the abbreviated full street name from the parsed abbreviated street name fields.
Before implementing triggering fields, all rules worked fine to update all fields when the parsed out abbreviated street name fields were updated.
After implementing triggering fields, the first and third attribute rules are set to use the abbreviated parsed street name fields as triggering fields and these work fine.
The second attribute rule is set to use the fully spelled out parsed street name fields as triggers. These should be "updated" by the first rule and then trigger the second rule, but it seems that edits made by other attribute rules are not recognized as direct updates for the triggering fields. The workaround was to add the abbreviated parsed street name fields as triggering fields for this rule, and it worked.
Have others noticed this as well?
I'm just wondering if this is by design where triggering fields don't seem to detect updates made by other attribute rules? I understand there could be something at play about the order of the rules but it seems like this should work based on the order I have defined. It could also be design to help avoid creating infinite loops, but I think in my example, it would not trigger an infinite loop. The workaround works...but it would be nice if the triggering fields recognized updates made by other attribute rules. Just wanted to see if others have run into this or if anyone from Esri has an any insight on this.
