Examkin

Question

Difficulty: Very hardCustom Fields and Data Types

An administrator at a healthcare company needs to revise several custom fields on the custom object Medical_Device__c to support a new regulatory compliance audit. The administrator plans to convert field types and reconfigure object settings. Which two technical impacts and data integrity risks must the administrator account for before changing custom field data types? (Select 2)

  1. Converting a field from Text to Picklist may result in data loss if existing text values exceed 255 characters or contain unsupported data formats.Answer
  2. Changing a custom field type from Auto-Number to Text retains existing data values but permanently prevents the field from generating incremental sequential identifiers.Answer
  3. C
    Converting a Roll-Up Summary field into a Lookup relationship field preserves all underlying child calculation logic automatically.
  4. D
    Converting a Picklist field into a Multi-Select Picklist automatically maps all picklist values to all existing Record Types without administrative intervention.
  5. E
    Converting a custom Lead field type automatically updates mapped custom Contact and Opportunity field types during Lead conversion.

Answer

Converting a custom Text field to a Picklist risks data loss for values exceeding 255 characters, and converting an Auto-Number field to Text retains existing values while halting automated sequence generation.
Converting a Text field to a Picklist restricts entries to a 255-character limit, causing data truncation or loss for longer values. Additionally, converting an Auto-Number field to a Text field preserves existing record data as text while stopping automatic sequential number generation for future records.

Step-by-Step Solution

1
Analyze data conversion rules from Text to Picklist.
Identified that text values longer than 255 characters are truncated or lost upon conversion to a single-select Picklist field.
Picklist fields impose a maximum length limit of 255 characters per entry.
2
Evaluate the structural impact of converting an Auto-Number field to a Text field.
Existing values are preserved as plain text strings, but future sequence numbering stops.
Text fields lack auto-increment engines required for sequential identifier generation.
3
Evaluate incorrect relationship and conversion assumptions.
Disqualified statements regarding automatic Roll-Up conversion, automatic Record Type assignment, and automatic Lead conversion mapping updates.
Salesforce requires explicit master-detail relationships for roll-ups and manual configuration for record types and lead field mapping.

Key Concept

Custom Field Data Type Conversion Consequences and Data Protection
Rate this question

Topics

Custom Fields and Data Types

More questions from this topic