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.
#372 - How to prevent duplicate records in mailchimp campaign activities details.
I decrease the SugarChimp - Initiate Campaigns Update Schedulers time to 3 min(default is 15 hours). I decrease the SugarChimp - Create For Each Campaign Update Jobs Schedulers time to 3 min(default is 3 hours).
Due to above i am getting duplicate records in mailchimp campaign activities. What is the best settings?Please provide!!!
-
"Support was fantastic. Great bit of programming and we will be using it for the foreseeable future."
Read More Reviews
- Most Recent Love from Users
melissa- Westcoat
- Mark Westerhoff
- danielolivas
- kgm
- Evolution Marketing
10 years ago
If i increased the time to 15 hours,after 15 hours also i will get duplicate records?
10 years ago
Hi inkriti, I would recommend leaving the schedulers at the default time intervals as they are installed. To get things back in sync, I would recommend you uninstall SugarChimp and reinstall the module. This process will remove the schedulers and recreate them as they should be. You will have to manually delete the duplicate records that you see.
The schedulers have to be run in a certain order and at a certain frequency for everything to work. In the next version of SugarChimp that will be for Sugar 7, SugarChimp will be much more flexible in regards to the schedulers.
10 years ago
Now schedulers at the default time intervals.But After 15 hours i am getting duplicate records(Sent,Opened,..etc).
10 years ago
Hello again, I'm going to follow up with an email regarding this issue to ask more questions. Thanks!
10 years ago
I wanted to post a brief update on this case. We were able to chat about the issue. I have the information I need now to properly debug what's going on. I'll report back when I have more info. Thanks!