Contact keeps reverting back to old info

Hi @doncullen,

It sounds like WooSync is updating your customer’s information based on the information on WooCommerce.

WooSync is intended to only sync one-way, from WooCommerce to Jetpack CRM. If you make any changes on Jetpack CRM’s side, that information will not be updated on WooCommerce customers’ information.

If you’d like to specify order mapping, you can do so in Jetpack CRM settings > WooCommerce Sync > Order Mapping:

—

For Prefix issue, I could replicate this issue on my end. What I did is as following:

1. Create an order for a WooCommerce Customer.
2. Run WooSync to sync the order and generate CRM contact
3. Add a prefix to the newly generated CRM contact
4. Create a new order for the same WooCommerce Customer
5. Run WooSync again and find the CRM contact’s prefix removed.

I suspect the issue here is that WooCommerce doesn’t store information for prefixes of their Customers, so the information is ‘wiped’ whenever WooCommerce generates a new order with its own Customer data (i.e., without a prefix). When WooSync runs, it reads WooCommerce’s customer data without a prefix, so it overwrites the prefix information.

While this is somewhat expected behavior (since WooSync only syncs WooCommerce data into Jetpack CRM, not the other way around), I’ll consult our team to see if this is an issue we can address.

—

Regarding “Photo”, I’m not sure what you’re referring to here. Is this a custom field set in Jetpack CRM? Or something else?

• This reply was modified 2 years, 1 month ago by Jay.
• This reply was modified 2 years, 1 month ago by Jay.

WooSync should be two way. If I change a customer’s name, it should also change it in WooCommerce. That’s the whole point of having Jetpack CRM integrate with WooCommerce. Otherwise it’s just a mask on WooCommerce and is of limited utility. I appreciate your running it by the dev team.

As for the photo, I’m talking about the contact photo you see at top right when editing a contact. Normally that uses gravatar, but I installed a plugin (Simple Local Avatars) that lets me use a photo from the media library as the contact’s photo. It works perfectly UNLESS the contact goes from a lead to a customer — in other words, now has info in WooCommerce, at which point their information is overwritten and lost, including the photo. I rely on photos to know who each contact is as I remember faces better than names. I suspect that when WooSync runs, rather than selectively updating, it simply updates the entire row in MySQL for that contact without bothering to check for fidelity issues.

A simple solution for this would be a basic two way sync; if a contact information changes within Jetpack CRM and that contact’s information exists in WooCommerce, it’d then update WooCommerce to reflect this change. This way when WooSync runs, it wouldn’t unilaterally nuke the contact’s information in Jetpack from orbit if it differs ever so slightly.

I’m a software engineer. It’d probably take me a hour or two to modify the plugin behavior so it’s two way sync. I won’t do that since any changes to the plugin would be overwritten when your plugin updates, hence my posting here asking you to please look into fixing it. If it’s something you’re NOT interested in fixing in the short term, please let me know so I can go ahead and hack the plugin and disable it from getting updates from you.

Thanks for getting back to me!

• This reply was modified 2 years, 1 month ago by doncullen.

@doncullen I agree with your point that this should be a two-way sync.

Hi @doncullen,

Thanks for your thorough and honest feedback. We already have an open feature request about this, so I added your +1 to it.

I have also added @farallon5’s +1 interest too ??

Let me know if you have any further questions or doubts, and we’re happy to assist you.

Can you please link to that open feature request? I believe you have a public tracker showing roadmap of planned features.

As you’re simply classifying this as a feature request and not as a bug (meaning will not fix the issue anytime soon), I will be moving ahead with modifying your plugin to support two-way sync and will be disabling your plugin from updating as this is not something I can simply wait a long time to see implemented.

Thanks for getting back to me.

• This reply was modified 2 years, 1 month ago by doncullen. Reason: fix typo

Hi @doncullen,

Due to the sensitive data included in the GitHub issues we create for CRM bugs and feature requests, our repo has to remain private, I’m afraid.

Let me know if you have any more questions or need some more help on this, otherwise I’ll mark the thread as solved for now ??

Hi @doncullen,

Good news — the fix for this issue you’ve reported was released in the latest release for Jetpack CRM core, v.5.5.

If you haven’t already done so, I recommend updating it to the latest version and giving it a try.

Thanks!

I can confirm the issues I previously raised are now all resolved. Thank you!

HI @doncullen ,

Glad to hear it, and thanks for checking out the new version.

I’ll close the thread since the issue it raised has been resolved with version 5.5.

Best,

Cena