Examkin

Question

Difficulty: MediumCustom Fields and Data Types

A Salesforce administrator at a SaaS enterprise management company is reviewing field configurations for lead conversion and custom field modifications on custom objects. Which TWO statements accurately describe the behavior and limitations of custom fields and data types in Salesforce? (Select 2)

  1. Custom Lead fields can be mapped to custom fields on the Account, Contact, or Opportunity objects during lead conversion, provided the target fields share compatible data types.Answer
  2. Converting a custom field type from Text to Picklist can cause data loss if existing text values exceed character limits or conflict with picklist configurations.Answer
  3. C
    Custom Lead fields can be directly mapped to Roll-Up Summary fields on the target Account object to aggregate converted lead metrics.
  4. D
    Newly added values in a custom picklist field are automatically assigned to all existing Record Types on the object upon creation.
  5. E
    Custom Lead fields automatically map to standard Account fields during lead conversion without requiring custom field mapping setup.

Answer

Custom Lead fields must be explicitly mapped to compatible custom fields on Account, Contact, or Opportunity objects during lead conversion, and converting field data types (such as Text to Picklist) carries potential data loss risks if existing data does not comply with the new data type requirements.
Custom Lead fields require explicit mapping to compatible custom fields on Account, Contact, or Opportunity objects. Furthermore, altering a custom field's data type, such as converting from Text to Picklist, presents data loss risks if existing records contain values that exceed length parameters or fail to match picklist entries.

Step-by-Step Solution

1
Analyze Lead field mapping rules during conversion
Confirm that custom Lead fields map to custom target fields of matching or compatible data types on Account, Contact, or Opportunity.
Salesforce Lead conversion field mapping enforces compatible data types between custom source and custom target fields.
2
Evaluate custom field data type conversion implications
Identify that converting data types (e.g., Text to Picklist) risks data loss when existing data exceeds limits or violates new validation requirements.
Salesforce alerts administrators that modifying custom field data types can result in data truncation or loss.
3
Evaluate incorrect options against Salesforce platform rules
Disqualify options suggesting direct mapping to Roll-Up Summary fields, automatic assignment of picklist values to all Record Types, or auto-mapping of custom Lead fields to standard fields.
Roll-Up Summary fields are read-only calculated fields, picklist values require explicit Record Type assignment, and custom Lead fields require manual mapping to custom target fields.

Key Concept

Custom Field Data Type Behavior and Lead Conversion Field Mapping Rules
Rate this question

Topics

Custom Fields and Data Types

More questions from this topic