An administrator at Cloud Kicks is asked to update a custom field on the Account object named `Account_Priority__c` from a Text data type to a Picklist data type to standardize reporting. Additionally, the administrator must ensure that during Lead conversion, the custom `Lead_Priority__c` field correctly populates this updated field on the created Account record. However, when attempting to change the data type directly in Object Manager, the administrator notices potential data preservation risks and field mapping constraints. Which sequence of actions must the administrator take to complete this requirement without losing existing data or breaking lead conversion?
- Change the custom field type from Text to Picklist on the Account object, define the required picklist values ensuring they match existing text data, update record type picklist assignments if record types exist, and map the custom Lead priority field to the Account priority field in Lead Custom Field Mapping.Cevap
- BMap the custom Lead priority field directly to the standard Account Type field in Lead Custom Field Mapping, avoiding the need to alter the Account custom field data type or record type picklist settings.
- CCreate a Roll-Up Summary field on the Account object that references the custom Lead priority field through a lookup relationship, bypassing the need for manual Lead conversion mapping.
- DChange the custom field type from Text to Picklist on the Account object, but omit assigning the new picklist values to Account record types because converting a field automatically makes all values available across all record types.
Cevap
The administrator must change the data type from Text to Picklist on the Account object, verify that the defined picklist API names match existing text entries, assign the picklist values to all active Account record types, and configure the custom field mapping on the Lead object to map to the Account picklist field.
Converting a custom Text field to a Picklist field is a valid administration operation in Salesforce. To ensure complete functionality, existing text values must correspond to the new picklist values, the values must be enabled for active record types on the object, and Lead custom field mapping must link the custom Lead field to the matching custom Account field.
Adım Adım Çözüm
Anahtar Kavram
Custom Field Data Type Conversion and Lead Field Mapping Constraints