A Salesforce administrator at a renewable energy company needs to update custom field configurations on the custom object Installation_Project__c and set up field tracking for prospective client leads. The administrator plans to convert an existing custom Text field to a Picklist field and configure custom lead field mapping for lead conversion. Which TWO statements accurately describe the technical considerations and limitations for these field changes?
- Converting a custom field from Text to Picklist preserves data, but values that do not match defined picklist entries will be lost if not explicitly added to the picklist value set.Cevap
- Custom lead fields can only be mapped to custom fields on the Account, Contact, or Opportunity objects during standard lead conversion.Cevap
- CA custom Roll-Up Summary field can be created on the Installation_Project__c object to aggregate data from a child object connected via a Lookup relationship.
- DDeleting a master record connected to an Installation_Project__c record in a Master-Detail relationship converts the child record into an independent record without deleting it.
- ECreating a new custom picklist field automatically assigns all available picklist values across all existing Record Types on the object.
Cevap
The correct statements are that converting a Text field to a Picklist field risks data loss for values not defined in the picklist value set, and custom lead fields can only be mapped to custom fields on the Account, Contact, or Opportunity objects during lead conversion.
Converting a custom Text field to a Picklist requires caution as data values not defined in the picklist set may be lost. Furthermore, standard lead conversion only maps custom lead fields to custom fields residing on the Account, Contact, or Opportunity objects.
Adım Adım Çözüm
Anahtar Kavram
Custom Field Data Type Conversion and Lead Field Mapping Capabilities