Resolve Lead Custom Field Mapping Errors

Common Causes & Solutions:

• Data Type Mismatch:

  • Cause: Mapping fields with different data types (e.g., text to number).

  • Solution: Ensure source and target fields have identical data types.

• Field Length Mismatch:

  • Cause: Source field length exceeds target field length, leading to truncation or errors.

  • Solution: Target field length must be equal to or exceed source field length.

• Decimal Place Mismatch:

  • Cause: Number, currency, or percent fields fields have differing numbers of decimal places.

  • Solution: Source and target numeric fields must have the same number of decimal places.

• Retroactive Errors from Pre-existing Mappings:

  • Cause: New, valid mappings may trigger errors due to non-compliant pre-existing mappings.

  • Solution: Verify all pre-existing mappings adhere to data type, length, and decimal place guidelines.

Resolution:

1. Review All Mappings: Navigate to the Lead Conversion Field Mapping page and inspect all involved fields.

2. Verify Data Types: Confirm source and target fields have matching data types. Adjust as needed.

3. Check Field Lengths: Ensure target field lengths accommodate source field lengths. Adjust as needed.

4. Align Decimal Places: For numeric fields, verify and standardize decimal places.

5. Audit Pre-existing Mappings: Critically review and correct any non-compliant pre-existing mappings.

6. Save Changes: Apply all adjustments to field mappings.

More Information:

• Refer to Salesforce Help & Training for "Guidelines for Mapping Custom Lead Fields for Lead Conversion" for detailed guidance