Why am I getting errors when saving Salesforce field mappings?

Last updated: April 27, 2026

Context

When configuring the Salesforce integration's field mappings for company data, you may encounter an error message when trying to save your mapping configurations, even though no specific error details are displayed.

Answer

If you're experiencing issues saving your Salesforce field mappings, this is typically related to permission settings for specific fields in Salesforce. Here's how to resolve this:

  1. Navigate to your Salesforce field mappings at Settings > Integrations > Salesforce > Mappings

  2. Review your field mappings to ensure you're only mapping to fields that your Salesforce user has permission to modify

  3. If you encounter a save error, try saving your changes in smaller batches to identify which specific field mapping might be causing the issue

Common issue with dropdown fields: If your field mappings include Salesforce dropdown (picklist) fields, these fields cannot be written to unless a default value is set in your mapping configuration. A common recurring issue involves billing country validation failures when the field values don't match your Salesforce picklist options.

To resolve dropdown field sync errors, you have two options:

  1. Set a default value – Configure a default value in your mapping that matches an accepted value in your Salesforce picklist (e.g., “United States” with proper formatting). This ensures records sync successfully even when the original value is empty or doesn't match your picklist options.

  2. Remove field requirement – Remove the dropdown field as a required field in your Salesforce configuration, allowing records to sync even when the field is empty or contains non‑matching values.

Specific Unify Field Mapping Recommendations for Salesforce Picklists

These recommendations help you align Unify fields with appropriate Salesforce picklist configurations.

  • Reply classification fields (Unify Initial Reply Classification, Unify Most Recent Reply Classification): These output one of five values—Positive, Objection, Neutral, Automated, or Negative. Create a Salesforce picklist with exactly these five values for cleaner reporting.

  • Sequence status fields: These output values such as Active, Paused, Finished: Completed, Finished: Replied, Finished: Bounced, Finished: Unsubscribed, Finished: Do Not Contact. Create Salesforce picklists with these exact values rather than using free‑text fields.

Fields that should use text instead of picklists: Unify Initial Reply Tags and Unify Most Recent Reply Tags are comma‑separated text fields that can contain multiple tags (e.g., “Ready to meet, Needs more information”). These should be mapped to text fields in Salesforce, not picklists, because the tag set is not a fixed finite list and can evolve over time.

Important: Multi‑select picklists are not supported and will cause sync failures. Additionally, Unify will not overwrite already‑filled Salesforce fields; it only writes to blank fields or on record creation.

Option 1 is recommended as it maintains data integrity while resolving sync failures.

If you continue to experience issues, verify your Salesforce user permissions for the fields you're attempting to map. Some fields in Salesforce may be read‑only or require special permissions to modify.