You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I've been using your plugin and found that it works really well except when it comes to labelled custom fields.
When a form field (CF7) is mapped to a Custom Field (CCF) on a form and the form is submitted, that field's data (CF7) is sent through to Constant Contact as "Custom Field 1". Now when managing contacts, it's often advised to rename the custom fields within Constant Contact. e.g. if I rename "Custom Field 1" to "Project Name" on Constant Contact, all contacts' custom field data is updated with the new label name. This is great and makes list management much easier - it also helps with Salesforce integration.
The problem arises when a new form submission is made after the renaming. The new submission now creates another Custom Field in Constant Contact called "Custom Field 1" - the field we previously renamed. Now my list data is going to be fragmented and old list members will have conflicting field labels with new list members, not to mention, it seems like I'm using more Custom Fields than I actually intended to.
I'm happy to assist with the coding but I'd like feedback on this first, is this expected behaviour? Should we allow users to name fields in the form settings? Is this a Constant Contact API limitation?
The text was updated successfully, but these errors were encountered:
Hello, I've been using your plugin and found that it works really well except when it comes to labelled custom fields.
When a form field (CF7) is mapped to a Custom Field (CCF) on a form and the form is submitted, that field's data (CF7) is sent through to Constant Contact as "Custom Field 1". Now when managing contacts, it's often advised to rename the custom fields within Constant Contact. e.g. if I rename "Custom Field 1" to "Project Name" on Constant Contact, all contacts' custom field data is updated with the new label name. This is great and makes list management much easier - it also helps with Salesforce integration.
The problem arises when a new form submission is made after the renaming. The new submission now creates another Custom Field in Constant Contact called "Custom Field 1" - the field we previously renamed. Now my list data is going to be fragmented and old list members will have conflicting field labels with new list members, not to mention, it seems like I'm using more Custom Fields than I actually intended to.
I'm happy to assist with the coding but I'd like feedback on this first, is this expected behaviour? Should we allow users to name fields in the form settings? Is this a Constant Contact API limitation?
The text was updated successfully, but these errors were encountered: