Automation rule executing 4 times for a user update :/

If you're updating the user via the /members/user profile tab, this is correct.  The page is built with multiple widgets that handle different sections of the user profile, so editing the profile on this page and saving, will cause the User.AfterUpdate event to fire 4 times.

Yeah, it is via that page.. I get 3 updates from the admin page.

Is there any way to suppress other events & only fire the rule once? I'd rather not call an external system 4 times if I'm doing that kind of integration via the automation rule.

Oh, and if my automation rule updates the user (maybe sanitising a field, or setting an Extended Attribute.. will it end up in an infinite loop?

There is not a way to suppress the events from firing multiple times as they are separate actions.  

If you're updating user data, then you should be using the BeforeUpdate and sanitize within the User.BeforeUpdate properties so another update action will not fire.
https://community.telligent.com/community/11/w/api-documentation/66153/user-beforeupdate-automation-event

Okay, thanks for clarifying. The documentation is generally pretty good, but it could really do with some examples (and best practice tips) to help newbies get started.

Brian Dooley We have similar requirement. When user updates his/her firstname and lastname the display name should get updated to [firstname] [lastname]. While implementing this through script we are also facing the similar issue (event firing multiple times and community is getting disconnected). We tried using the API event User.BeforeUpdate but it is not helping. Can you please let us know how to sanitize within the User.BeforeUpdate properties so another update action will not fire?
 

Brian Dooley We have similar requirement. When user updates his/her firstname and lastname the display name should get updated to [firstname] [lastname]. While implementing this through script we are also facing the similar issue (event firing multiple times and community is getting disconnected). We tried using the API event User.BeforeUpdate but it is not helping. Can you please let us know how to sanitize within the User.BeforeUpdate properties so another update action will not fire?
 

1.On User.BeforeUpdate event you can get data that was going to be updated.

2.You can retrieve the old data of the user using core_v2_user.Get("%{ Id = $idArg }") 

Now as per your requirement check both the profile fields (first name, Lastname )  if there was a change then map the display name 

context_v2_automationTrigger.Arguments.DisplayName = first name +  Lastname

Thanks Satish Polampalli 3sides for your input. This will help.