Hi,

Is there a way of deactivating the recent update that syncs the WP User with the Amelia Customer information?

I can see how useful it would be for most however our use case is different and the first name of the Amelia Customer shouldn't match the first name of the WP User. All other details are fine but those two I can't have syncing and I'm having to go into the database each time we modify a user to then change their name back to what we need it to be.

Thanks very much.

Hi Marko,

Thanks for the reply. Updating the WP User also updates the Amelia Customer so that doesn't seem to work?

For clarity:

1. A Customer record is updated in Amelia
2. This then draws the WP User first name in to the Amelia database
3. So, I then change the Customer first name in Amelia back to the name it should be (in our case a Pet's name)
4. This then updates the WP User first name to the Pet's name when WP User should be the Owner's name
5. So, I go into the WP User section and update the User first name back to the Owner's name
6. This then updates the Amelia database back to the Owner's name rather than the Pet's name

And so the cycle goes on.

Is there a function, action, or trigger of some kind I can tap into via additional PHP code to break this cycle?

I completely get the modification when a Customer's name is the same as the WP User's name, but our use case doesn't reflect this and it's becoming really problematic. I'm happy to create a custom PHP snippet that interacts with the Amelia process if you can provide guidance as to what to target?

I'm updating this as a public reply because there is/was a solution to this using a combination of WP hook and the Amelia Developers Documentation:

Turn Off Customer to WP User Sync

• Using the Webhook "amelia_before_customer_updated" run a SELECT query for the wp_usermeta table to get the meta key values required based upon the externalId parameter shared by the filter. Then store it as a custom meta value for the User to be used later. This is all run before the Customer updates in the database.
• Then, using the Webhook "amelia_after_customer_updated" set the user meta using the stored data essentially overwriting the data that has been changed by the Amelia customer sync process.

Turn Off WP User to Customer Sync

• Add a PHP code snippet with the following: 
  remove_action('profile_update', ['AmeliaBooking\Infrastructure\WP\UserService\UserService', 'updateAmeliaUser'], 10, 3);

---

The WP User <-> Amelia Customer sync addition is absolutely essential for most use cases but the above provides a reverse engineering solution should it be required. A good understanding of the Amelia database structure is fairly useful, as is the ability to write custom PHP snippets.