Examkin

Question

Difficulty: MediumCustom Fields and Data Types

An administrator at a telecommunications provider is modifying custom fields on the custom object Equipment_Order__c to support a operational system migration. The administrator needs to convert an existing Picklist field named Priority_Level__c into a Multi-Select Picklist, and convert an existing custom Text field named Device_Tracking_ID__c into an Auto-Number field. Which TWO considerations or system behaviors should the administrator expect during these custom field conversions? (Select 2)

  1. Converting a Picklist field to a Multi-Select Picklist field preserves existing values on records, but can break existing validation rules or formula fields that reference the original field.Answer
  2. B
    Converting a Lookup relationship field to a Master-Detail relationship field automatically populates roll-up summary values for existing records even if some child records have blank parent references.
  3. Converting a custom Text field to an Auto-Number field leaves existing text values on historical records unchanged, while applying the auto-number formatting sequence to newly created records.Answer
  4. D
    Converting Lead custom fields automatically creates matching target custom fields and field mappings on Contact and Opportunity objects during lead conversion.
  5. E
    Converting a single-select Picklist to a Multi-Select Picklist automatically assigns all existing values across all active Record Types without requiring manual record type picklist assignment.

Answer

Converting a Picklist field to a Multi-Select Picklist preserves existing values on records, but can break existing validation rules or formula fields that reference the original field, AND converting a custom Text field to an Auto-Number field leaves existing text values on historical records unchanged, while applying the auto-number formatting sequence to newly created records.
Converting a Picklist field to a Multi-Select Picklist preserves data on existing records, but formulas or validation rules referencing the original field will fail if they use single-select functions like ISPICKVAL instead of multi-select functions like INCLUDES. Furthermore, converting a Text field to an Auto-Number field retains existing text values on historical records while applying the sequential auto-number format exclusively to newly created records.

Step-by-Step Solution

1
Analyze the impact of converting a single-select Picklist field to a Multi-Select Picklist field.
Existing record values are preserved, but functions such as ISPICKVAL in formulas and validation rules will fail or produce syntax errors because multi-select picklists require the INCLUDES function.
Salesforce handles data preservation for picklist conversions, but formula syntax rules differ between single-select and multi-select picklist data types.
2
Analyze the impact of converting a custom Text field to an Auto-Number field.
Historical text values remain unaffected on pre-existing records, while new records generated post-conversion automatically populate using the newly defined auto-number sequence format.
Salesforce preserves historical text data when converting to Auto-Number to prevent data loss.
3
Evaluate and eliminate distractors related to relationship limitations, lead mapping, and picklist record type configurations.
Confirmed that converting lookup to master-detail requires non-null parent values, lead field mapping requires explicit target setup, and picklist record type availability must be verified.
Identified standard Salesforce administrative limitations across object management and field conversions.

Key Concept

Custom Field Data Type Conversion Rules and Considerations
Rate this question

Topics

Custom Fields and Data Types

More questions from this topic