Hi, I am trying to update custom fields for contacts between sends. If I add a contact via the bulk API, send a message, and then add the user again later with additional custom fields (in hopes of updating the user), those new custom fields aren't added.
Here's a sample test script which adds a user via the bulk API, prints its custom fields, adds it again with a new custom field, and prints its custom fields again. After "uploading file 2", it should show an additional line, CustomField2 = field2, but does not.
Hello,
After looking over your code and your description of what you are seeing, it looks and sounds like you are experiencing a new issue that we are tracking right now. The easiest way to verify this is for you to email us with some additional details at webservices@constantcontact.com so that I can verify. The information that we would need is:
- Constant Contact Username
- Example Email Address used to test the script
Please feel free to include any questions that you may have as well.
Best Regards,
Any updates on this? I have a client that is facing a major delay on a pretty big promotion they are running due to this issue.
I am assuming the issue mentioned here with the API is related to the same issue that occurs when trying to import new custom field data using the CC web interface, where existing contacts that do not already have a value assigned to that field do not import the new custom field.
I was actually only looking into using the API and building a custom app simply as a workaround to the web interface import bug, but now it looks like it would not work using the API either. Can you please confirm?
Thanks,
Mark Mitchell
Hi Mark,
With the issue you are discussing, it will unfortunately impact an API integration as well. This is because the issue is happening within the system which processes import activities, and thus it will affect both file uploads through the UI and bulk imports from the API. The good news to be had is that we do have developers working on this issue right now, and we hope to have a fix deployed for this near the end of the month.
Sincerely,