Save Your Team Countless Hours. SugarChimp syncs your lists in both directions so you can work in your preferred app. Segment and group your Mailchimp subscribers based on Sugar data so you can market to the right people at the right time. Compatible with all versions and editions of Sugar and SuiteCRM. Created by Fanatical Labs, 2023 SugarCRM Partner Award Winner.
#3081 - Field/group values reverting after changes in the CRM
Hello,
We have begun to notice that updated field values within the CRM revert back to their previous values after SugarChimp runs. This has been verified using Sugar's field auditing capabilities. We clearly see the CRM values are changed as requested by the CRM user, then, a few minutes later changed back by an automated process. I disabled the SugarChimp scheduler to verify if it was this process causing the reversion. Once disabled, the reversions stopped.
It would appear that the update to MailChimp is somehow triggering SugarChimp to switch back some or all of the values to those stored in MailChimp. This does not occur consistently, and some fields are effected more often than others. Amongst the values most commonly effected are multi-select fields which are synced up to MailChimp groups. Although, standard text fields have also been effected.
I would appreciate any guidance you may have to resolve the issue.
Thanks.
Tom.
-
"We do a lot of highly-segmented outbound marketing and SugarChimp is exactly what we needed. The list and field syncing are great, and it allows us to do more sophisticated campaigns that exactly target certain Lead profiles in Sugar. The SugarChimp team is also really great, and they are totally committed to our success."
Read More Reviews
- Most Recent Love from Users
melissa- Westcoat
- Mark Westerhoff
- danielolivas
- kgm
- Evolution Marketing
7 years ago
Hello Tom,
I apologize for the troubles and will help you get to the bottom of the issue. It sounds to me like there is the potential for multiple Sugar instances to be syncing up with the same MailChimp List (dev instance perhaps?). The quickest way we can figure this out would be to hop on a screenshare. Can you schedule a time for us here: https://calendly.com/fanaticallabs/sugarchimp-support
I think we'll be able to figure out what's going on and get it lined out. Let me know if you have trouble with the schedule and we can figure something else out.
Thanks, Jon
7 years ago
Hi Jon,
I've scheduled an appointment. Over the past few days, we've been cleaning up our database and disabling our test instances. I've also reset the MailChimp API key so that only the production version as the new key (to make absolutely sure no other instance was able to communication with MailChimp). The same behaviour is continuing to be experienced.
Tom
7 years ago
Thanks, Tom. That was a very good idea, clearing the api keys. It would've been the first thing to do on the call. We will be able to turn the logging up and figure out what process is causing the problems. I look forward to talking with you soon and getting it figured out.
Thanks, Jon
7 years ago
Hello Tom,
To update the support case, we were able to get on a call and find that the issue occurred whenever odd data in the database was present for the multiselect fields. Whenever the multiselect field data was good, the error didn't seem to occur. You were going to look at cleaning up the process that set the data on the multiselect field and let us know what you found.
Were you able to update your customization yet? Have you been able to replicate the issue since that point? Let me know if you need anything else.
Cheers! Jon
7 years ago
I'm going to go ahead and close this case out. If anything else comes up during your changes, let us know.
Thanks, Jon