A Salesforce administrator at an industrial aerospace manufacturing company is configuring lead conversion settings to transfer custom qualification data from Lead records to Account and Opportunity records. The Lead object includes a custom picklist field, Deployment_Scope__c, which needs to populate corresponding target records upon conversion. Which two technical constraints and behaviors must the administrator consider when configuring Lead Custom Field Mapping and conversion settings?
- Custom fields on the Lead object can only be mapped to custom fields on the Account, Contact, or Opportunity objects.Answer
- If a target custom picklist field enforces restricted picklists, lead conversion will fail if the converted Lead contains a picklist value that is not active on the target picklist field.Answer
- CCustom Lead picklist fields can be directly mapped to standard Account picklists using standard Lead Custom Field Mapping if their data types match.
- DConverting a lead automatically dynamically assigns and activates missing picklist values within the target object's active Record Type picklist configuration.
Answer
The correct configurations to consider are that custom Lead fields can only be mapped to custom fields on target objects, and that target picklist fields enforcing restricted picklists will cause conversion to fail if the Lead contains an inactive or unlisted target picklist value.
Lead conversion mapping requires custom fields on the Lead to be mapped strictly to custom fields on Account, Contact, or Opportunity records. Furthermore, when converting data into custom target picklists with restricted picklists enabled, all values transferred from the Lead must exist as active values in the target picklist set; otherwise, the platform will block record creation and throw a conversion error.
Step-by-Step Solution
Key Concept
Lead Custom Field Mapping Restrictions & Picklist Validation Rules