Examkin

Question

Difficulty: HardCustom Fields and Data Types

A Salesforce administrator at a subscription management company needs to update custom field settings on the custom object Subscription_Contract__c to align with updated accounting requirements. The administrator plans to convert an existing Text field used for storing promotional codes into a Percent field, and convert an Auto-Number contract identifier field into a Text field.

Which two statements accurately describe the consequences and considerations of these custom field data type conversions?

  1. Converting an Auto-Number field to a Text field preserves existing values in current records, but disables automatic sequential numbering for newly created records.Answer
  2. Converting a Text field to a Percent field results in data loss for any records containing non-numeric characters or text strings.Answer
  3. C
    Deleting a custom parent record linked through a Lookup relationship automatically deletes all associated child records on Subscription_Contract__c.
  4. D
    A Roll-Up Summary field can be configured on a parent object to calculate total contract values from child records connected only via a Lookup relationship.
  5. E
    Converting a custom Picklist field to a Multi-Select Picklist automatically grants picklist value access across all Record Types without requiring manual configuration.

Answer

Converting an Auto-Number field to a Text field preserves existing data while stopping auto-numbering on future records, and converting a Text field to a Percent field leads to data loss on records containing non-numeric values.
Converting an Auto-Number field to a Text field retains all existing values on current records, but turns off automated sequential number generation for new records. Converting a Text field to a Percent field converts numeric values successfully, but causes data loss on any record containing non-numeric text characters.

Step-by-Step Solution

1
Analyze the impact of converting an Auto-Number field to a Text field.
Recognize that existing text values are retained on historic records, but future record creations will no longer generate automatic sequential numbers.
Salesforce allows Auto-Number to Text conversion while retaining data, but the auto-numbering logic is disabled.
2
Analyze the impact of converting a Text field to a Percent field.
Identify that non-numeric text strings cannot be converted into numbers, leading to data loss on affected records.
Data type conversions from broad types (Text) to restrictive numeric types (Percent/Number/Currency) lose non-convertible data.
3
Evaluate relationship and picklist field limitations presented in distractor options.
Confirm that cascading deletes and roll-up summaries depend on Master-Detail relationships, and picklists require explicit Record Type assignment.
Eliminates incorrect statements regarding Lookup relationship capabilities and Record Type picklist management.

Key Concept

Salesforce Custom Field Data Type Conversion Rules and Data Loss Considerations
Estimated Time:2m 0s
Rate this question

Topics

Custom Fields and Data Types

More questions from this topic