A Salesforce administrator at a specialized medical equipment supply enterprise is setting up Lead Custom Field Mapping for sales operations. The team requires a custom picklist field on the Lead object named "Procurement Model" to automatically populate a corresponding field on the Account record whenever a lead is converted. While attempting to map the fields in Setup, the administrator finds that the target custom field on the Account object is missing from the mapping dropdown menu for the "Procurement Model" field.
Which configuration mismatch is preventing the custom Account field from appearing in the lead field mapping selection?
- The custom field created on the Account object has a Text data type rather than a Picklist data type.Answer
- BThe custom lead field was already mapped to a custom Opportunity field before configuring the Account mapping.
- CThe picklist values of the target Account field have not been assigned to the active Account record types.
- DThe target Account field was not added to an active Sales Process prior to configuring lead conversion settings.
Answer
The custom field created on the Account object has a Text data type rather than a Picklist data type.
In Salesforce Lead Custom Field Mapping, source custom fields on the Lead object can only be mapped to custom target fields on the Account, Contact, or Opportunity objects that share identical or compatible data types. Because the source field on the Lead is a picklist, the target Account field must also be created as a picklist. If the Account field was created with a different data type (such as Text), Salesforce will exclude it from the mapping dropdown menu for that picklist field.
Step-by-Step Solution
Key Concept
Lead Custom Field Mapping Data Type Compatibility
Estimated Time:1m 30s