We have a working bulk upload process using the api and a csv file. We recently tried adding two custom fields to the process and our uploads will not process when those two custom fields are included.
The two custom fields were added using the new contact mangement UI, so they have been named D_ID and P_ID
We named the fields CustomField1 and CustomField2 in the process after trying the process using the above custom names, the process fails with CustomField1 and/or D_ID.
I read your post that was something like ours but it dodn't indicate if anything worked or not.
How should we be naming the fields?
If you look at our documentation here: http://developer.constantcontact.com/docs/bulk_activities_api/bulks-activities-import-contacts-api.h..., you'll see the currently suppored formats. We do intend to add support for additional Custom Fields once we have completed our migration to our new Contact Management platform. Currently a segment of our customers are still on the older platform and are not able to use named custom fields, which is why we are still not able to support that feature.
It worked when changed to Custom Field 1, including the spaces. We want to use these fields in a dynamic link, but have had no luck yet. Here is how our URL looks:
We get the first name fine but no text from custom field 1.
Is this a syntax issue? If yes, how should the custom field 1 be written in a dynamic link (querystring)?
That's a great question. I'm not sure how the query strings have been changed in our editor to work with the new Contact Managment platform (or if they have yet). Will check with that team and see if I can get you an answer.