A Salesforce administrator at a heavy equipment rental enterprise is setting up Lead Custom Field Mapping to support lead conversion. The sales operations team specifies that a custom picklist field on the Lead object named 'Equipment Class' must populate a custom field on the target Account record upon conversion. However, when configuring the field mapping under Lead Settings, the administrator observes that the desired custom Account field is missing from the target picklist field dropdown menu. What is the root cause preventing the Account field from appearing as a mapping target?
- The target custom field on the Account object was created as a Text data type instead of a Picklist data type.Answer
- BThe custom Account field has not been assigned to the default Account Record Type used by the sales team.
- CThe custom Lead picklist field has not been mapped to an active Sales Process on the Opportunity object.
- DThe administrator forgot to select the field mapping checkbox inside the Lead Conversion Settings page before creating the field.
Answer
The target custom field on the Account object was created as a Text data type instead of a Picklist data type.
In Salesforce Lead Custom Field Mapping, custom fields on the Lead object can only be mapped to custom fields on the target Account, Contact, or Opportunity objects if their data types match. Specifically, a custom Picklist field on the Lead object must be mapped to a custom Picklist field on the target object. If the target Account field was defined as a Text data type, Salesforce automatically excludes it from the selection list for the Lead Picklist field.
Step-by-Step Solution
Key Concept
Lead Custom Field Mapping Data Type Restrictions
Estimated Time:2m 0s