A Salesforce administrator at a B2B agricultural equipment manufacturer is configuring lead conversion settings to transfer qualified prospect data across the revenue lifecycle. The sales team requires custom data captured on Lead records—including equipment preference picklists and annual fleet budgets—to map over to newly generated records upon conversion. Which two statements accurately describe the system rules and behaviors governing custom Lead field mapping?
- A single custom Lead field can be mapped simultaneously to one custom field on the Account, one custom field on the Contact, and one custom field on the Opportunity.Answer
- The source custom Lead field and target custom fields on destination objects must share matching data types, such as mapping a custom Picklist to a custom Picklist.Answer
- CCustom Lead fields can be mapped directly to existing standard fields on the Account or Contact records as long as their data types are identical.
- DA custom Lead field can be mapped to multiple custom fields on the same target object to populate different record types dynamically.
Answer
The correct statements are that a single custom Lead field can be mapped to one custom field on the Account, Contact, and Opportunity objects simultaneously, and that the source and target custom fields must share compatible data types.
Salesforce Lead Custom Field Mapping allows administrators to map each custom field on the Lead object to one custom field on the Account, one custom field on the Contact, and one custom field on the Opportunity concurrently. Furthermore, field mapping enforces data type alignment, requiring source and target fields to share identical or compatible data types.
Step-by-Step Solution
Key Concept
Lead Custom Field Mapping Rules and Data Transfer Capabilities
Estimated Time:1m 30s