Question

Difficulty: MediumCustom Fields and Data Types

Northern Trail Outfitters is planning modifications to custom field configurations on their custom Asset Management object. Which two statements correctly describe the behavior and limitations when managing custom field data types and conversions in Salesforce? (Select 2)

  1. Converting an Auto-Number field into a Text field preserves existing record data values without causing data loss.Answer
  2. Converting a single-select Picklist field into a Picklist (Multi-Select) field preserves existing picklist values on current records.Answer
  3. C
    Creating a Roll-Up Summary field is supported on a parent object connected to child records through a standard Lookup relationship.
  4. D
    Custom lead fields automatically map to corresponding custom account, contact, and opportunity fields during lead conversion without manual mapping.
  5. E
    Adding a new value to a master custom picklist automatically assigns that value to all existing Record Types for that object.

Answer

The correct statements are that converting an Auto-Number field to a Text field preserves existing data, and converting a single-select Picklist to a Multi-Select Picklist retains existing values on records.
Converting an Auto-Number field to a Text field preserves existing record numbers while allowing manual editing moving forward. Similarly, converting a Picklist field to a Multi-Select Picklist maintains existing single-select choices on saved records without data loss.

Step-by-Step Solution

1
Analyze field data type conversion safety rules for Auto-Number and Picklist fields.
Auto-Number to Text conversion is safe and maintains existing data. Converting a single-select Picklist to a Multi-Select Picklist also preserves existing value selections on records.
Salesforce allows seamless conversion between compatible data types where data truncation or structural mismatch does not occur.
2
Evaluate relationship requirements for Roll-Up Summary fields.
Roll-Up Summary fields are restricted to Master-Detail relationships.
Lookup relationships do not enforce strict parent-child data tightness required for native roll-up summary calculations.
3
Evaluate administrative requirements for Lead field conversion and Record Type picklist assignments.
Both custom Lead field conversion mapping and Record Type picklist value assignments require explicit administrator configuration.
Salesforce does not automatically assume target conversion destinations or record type availability for new custom field values.

Key Concept

Custom Field Data Type Conversions and Limitations
Rate this question