Why do I get a "No such column" error for a Salesforce field that actually exists?
If the field name and suffix are already correct, the real cause is almost always that the Salesforce user running that part of the sync doesn't have field level security (FLS) read access to that field. Salesforce returns the same "No such column" style error whether a field is misspelled or simply hidden from that user, so a correct field like can trigger it just as easily as a typo.
Running the Data Wizard
If this happens on a Data Wizard job, all fields mapped in wizards need to be readable by the Run As user for that wizard, not just whoever set the wizard up.
Acting as the Sync User
If the error comes from the background primary sync, check field level security for your designated Sync User. The primary sync pulls data from Mailchimp to Salesforce, matches contacts or leads, and then runs any mappings set in that direction. That user's profile or permission set needs Edit access to any Salesforce field involved in matching incoming members or mapping data from Mailchimp to Salesforce.
Triggering Salesforce to Mailchimp Field Mappings
Field Mappings [Full Guide from Salesforce to Mailchimp are used in the following scenarios:
- Managing a member on their contact's component
- Editing a record with a related member
- Triggering a membership invocable action
These things all run in the current user's own security context, not as the admin. Check that the person using these features has Read access to every mapped field. They will also need one of our permission sets.
In every case, the fix is the same: grant Read access to that field.
Related Articles
• Why am I getting a "MC4SF_WIZARD_SOQL_SETUP_ERROR" error on my Data Wizard job?
• What is the Mailchimp Limited permission set and what can a Limited user do?
