An administrator at Zenith Logistics is attempting to change the data type of a custom field named `Priority_Score__c` on the Lead object from Number to Picklist. However, the conversion attempt fails. Upon investigating the setup, the administrator notes that `Priority_Score__c` is mapped to a custom Opportunity field for lead conversion and is also referenced in a calculation on a related object. What is the primary reason Salesforce prevents this custom field data type conversion?
- Salesforce restricts changing a custom field's data type while it is referenced by dependent components such as lead field mappings or roll-up summaries, requiring those references to be removed first.Cevap
- BRoll-up summary fields support picklist data types only when the relationship between the objects is defined as a Lookup relationship rather than a Master-Detail relationship.
- CCustom Lead fields converted to a Picklist data type are required to map directly to standard Opportunity fields rather than custom fields during lead conversion.
- DConverting a field to a Picklist is blocked until the new picklist values are explicitly assigned to all active Record Types on the target object.
Cevap
Salesforce prevents data type changes on custom fields whenever dependent references exist, such as lead conversion field mappings or roll-up summary fields. These dependencies must be removed before the field type can be converted.
Salesforce strictly blocks data type changes on any custom field that is actively referenced by other metadata components, including lead field mapping, roll-up summary fields, formula fields, Apex classes, or process automation. The administrator must first delete or remove these dependent references before successfully changing the field's data type.
Adım Adım Çözüm
Anahtar Kavram
Custom Field Data Type Conversion Restrictions and Metadata Dependencies