chrisquinnr does not have any add-ons for sale.

• Only syncing 2097 leads out of a possible 2762

  Support November 4th, 2014 @ 5:58 pm
  

  Hi,

  Unfortunately no luck.

  The problem seems to revolve around date formatting. When the data comes across to Mailchimp, it appears that dates which would violate US time/date settings (mm/dd/yyyy) are not stored.

  For example, using

  In Sugar, a record has a date created of 09/10/2014 => imported into mailchimp as 09/10/2014 In Sugar, a record has a date created of 24/10/2014 => not imported

  (The latter case would obviously not make any sense in US format, so is not recorded..?)

  I've tried setting the date format in MailChimp to dd/mm/yyyy and re-syncing the two lists, but this does not appear to fix the issue. Our Sugar installation is hosted so I don't think I can get at the database directly to check how the date is stored.

  Date_entered (what we know as Date Created) is a Sugar-generated field so I'm at a loss as to how we can influence things further. There is an Admin option to change the display of dates, but given the range of options I'm guessing this interprets the stored data as opposed to affecting how the date itself is stored.

  I guess I've got the following question: - When data is synced from Sugar to MailChimp, does the SugarChimp plugin perform any comparison or conversion of dates on the way over?

  Thanks

  View Comment
  
  
• Only syncing 2097 leads out of a possible 2762

  Support October 23rd, 2014 @ 4:24 pm
  

  Not yet, we're waiting for an opportunity to change the format of the date field in Sugar to be British style, as opposed to US style (or whichever way will make the two lists agree) as our thinking is that this could be an issue.

  Based on your feedback above and the fact that the data comes across wholesale as a text field, the issue must be data related.

  Would you mind if we left this open for the minute so as we can update this thread with the results of our investigation?

  View Comment
  
  
• Only syncing 2097 leads out of a possible 2762

  Support October 21st, 2014 @ 11:46 am
  

  Hi again,

  Thanks for your response above, the data was indeed the cause of the disparity in numbers. I have a further question, which I'll put below, but please let me know if you'd like it moved to a new thread.

  (oh and I've emailed support as you've request above with the license key)

  Our further question is around date fields - for Leads in Sugar there is a date created field (the slug being date_entered), and we've set up the field mapping to synchronise this field to a corresponding date field in MailChimp.

  However, the date only appears to synchronised into MailChimp for around half of the leads. Is there an existing bug for this issue or is likely to be related to our set up?

  To further test the issue I created a new column to sync with date created, but as a text field. In this instance, all the correct dates came across into Mailchimp, but as it is a text field, we cannot segment by date.

  Again, I'd be grateful for any pointers.

  View Comment
  
  
• Only syncing 2097 leads out of a possible 2762

  Support October 15th, 2014 @ 12:00 pm
  

  Hi, To each question in turn:

  • We used step 4 to import from Sugar to Mailchimp.
  • Yes, they added 700 subscribers to the target list and we were expecting them to appear in Mailchimp
  • Do you want me to put the license key here in plaintext or should I send it to you more securely?

  We've since identified that the problem was a limit on the client's account - they only had a free account so were limited to 2000 subscribers. Now that this problem is removed though, we still only have a reduced percentage of leads coming through.

  Could you answer the following for me?:

  If no email address is set against the lead in Sugar, will it come into Mailchimp or will it be skipped?

  Thanks

  View Comment
  
  

chrisquinnr has not rated any add-ons.

chrisquinnr has not verified any add-ons.

chrisquinnr has not created any Wanted Add-ons.