Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Search instead for
Did you mean:
Constant Contact wants to help you succeed! We’re celebrating our professional service programs on the Constant Contact Community this month and you have a chance to try one of the services for free! Learn more.
Hi Jimmy_D, Thanks for your answer. Fields are created separately and we are able to set them by updating contact directly. When we try to insert contacts using JSON bulk activity, fields are mapped into wrong properties (not omitted). cf:td_velocity (field with td_velocity name of type string exists) value is being set as a city (in address). This doesn't sound you like a possible bug in JSON bulk activity? Thanks, Sveta
... View more
Hi, We are trying to Import Contacts Using JSON, and set custom fields as stated in documentation: cf:custom_field_name optional, Max. Length:255 This header column name is the name of an existing custom field prefixed with cf:. For example, enter cf:first_name if you have a custom field named “first_name”. As long as you use the cf: prefix, you can import custom fields that use the same name as the contact properties. You can add up to 25 different custom field headings for each contact. Problem is that not all custom fields are set. We are not exceeding limit of 25 fields per contact. We have two fields, both of them are "string" type, first is set, and second is not. There is noting special about field names (td_longevity, td_velocity), and both values are sent as strings. Activity summary shows no error. If we try to update single Contact, both custom fields are set correctly. Is there some non-documented restriction in field names when using bulk api? What could be the problem causing td_velocity not to be saved? EDIT: When using Import Contacts Using JSON it seems that system is updating wrong property. cf:td_velocity value is written into street_addresses.street_address.city. Regards, Sveta
... View more