Troubleshooting Contact and Playbook Data Sync Issues with Salesforce

If you're experiencing issues with contacts and playbook data not syncing properly between Unify and Salesforce, there are several common causes and solutions to resolve these sync failures.

Field Mapping Configuration Issues

One of the most common causes of sync failures is incorrect field mapping configuration. If a field like 'Last Name' is set to 'read only' in Unify's person-level mapping, but Salesforce has validation rules requiring that field to be populated for record updates, the sync will fail.

Solution: Update the field mapping in Unify from 'read only' to 'read & write' for any fields that are required by Salesforce validation rules. This ensures that Unify can properly write back data to Salesforce without violating validation requirements.

Billing Country Validation Issues

Salesforce writeback failures frequently occur due to billing country field validation issues. There are two approaches to resolve these failures:

Option 1: Set a Default Value (Recommended)

Configure a default value that matches an accepted value in your Salesforce billing country picklist (e.g., "United States" with proper formatting). This ensures writebacks succeed even when records lack billing country data or have non-matching values.

Option 2: Remove Field Requirement

Remove billing country as a required field for person-level writebacks in your Salesforce configuration, allowing records to sync successfully even with empty or non-matching billing country values.

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

Missing Required Fields

Account and contact sync failures can occur when required fields are missing from the data. Most importantly, accounts must have a name field populated for successful sync to Salesforce. If the account name is missing, both the account and associated contacts will fail to sync as a cascading effect.

This commonly happens during CSV uploads when the company name field is not properly mapped during the import process.

To prevent these sync failures:

• Ensure that all required Salesforce fields (particularly account names) are populated before attempting to sync

• Verify that company name mapping is properly configured during CSV uploads

• Review data completeness before initiating sync operations from Unify to Salesforce

Company-Contact Association Issues

Avoid using bulk placeholder companies for large numbers of contacts, as this can cause cascading sync failures. Instead, configure Unify to automatically create individual company records for contacts when the associated company doesn't exist, rather than associating them with a single placeholder company.

If a company record sync fails partway through, it can leave the record in a stuck state that blocks writebacks for all associated contacts. This creates cascading failures since contact syncs depend on their parent company being written first.

Best Practices for Preventing Sync Issues

• Regularly review and update field mapping configurations to ensure they align with Salesforce validation rules

• Maintain data quality by ensuring required fields are populated before syncing

• Use individual company records rather than bulk placeholder companies

• Monitor sync logs for early detection of validation or configuration issues

By addressing these common causes - field mapping configurations, validation requirements, data completeness, and proper company-contact associations - you can resolve most contact and playbook data sync failures between Unify and Salesforce.