An administrator at Universal Containers created a custom Picklist field on the Lead object named 'Preferred Service Level'. The business requirement specifies that when a Lead is converted, the selected value in this custom field must automatically populate onto the newly created Contact record. During testing, the administrator observes that converted Contact records are created with a blank 'Preferred Service Level' field. Which configuration mistake accounts for this behavior?
- The administrator failed to map the custom Lead field to a compatible custom field on the Contact object in the Lead Custom Field Mappings setup.Cevap
- BThe custom picklist values were successfully added to the Lead field but were omitted from the default Contact record type picklist assignment.
- CThe target field on the Contact object was created using a Lookup relationship to the Lead object instead of a Master-Detail relationship.
- DThe Lead record conversion process encountered cascading deletion rules because the Lead was not detached from a master parent object.
Cevap
The custom Lead field was not mapped to a compatible custom field on the Contact object within the Lead Custom Field Mappings administration settings.
The correct answer highlights that custom fields on the Lead object must be explicitly mapped to custom target fields on the Account, Contact, or Opportunity object using the 'Map Lead Fields' tool under Lead Object Manager. Without this mapping, custom lead field data is ignored during the conversion process.
Adım Adım Çözüm
Anahtar Kavram
Custom Field Mapping during Lead Conversion
Tahmini Süre:2m 0s