Examkin

Question

Difficulty: HardCustom Fields and Data Types

A Salesforce administrator at a renewable energy firm is configuring custom fields on the Lead object to support a new solar installation tracking initiative. The administrator must map custom Lead fields for conversion to target objects and modify existing custom field data types on the Lead object. Which two statements accurately describe the technical behavior and considerations for custom field mapping and data type changes in Salesforce? (Select 2)

  1. Custom Lead fields can be mapped to custom fields on Account, Contact, or Opportunity records if both fields have matching data types or compatible conversion targets.Answer
  2. Changing a custom field data type from Text to Picklist may result in data loss if existing record values do not match defined picklist values or length constraints.Answer
  3. C
    Custom Lead fields can be mapped directly to Roll-Up Summary fields on the Opportunity object to dynamically aggregate converted lead metrics.
  4. D
    Unmapped custom Lead fields automatically generate new custom fields on the target Contact record during the conversion process.
  5. E
    Adding new values to a custom Picklist field automatically assigns those values to all existing Record Types on the target object.

Answer

The correct statements are that custom Lead fields can be mapped to custom fields on Account, Contact, or Opportunity records with compatible data types, and changing a custom field data type from Text to Picklist can cause data loss if existing data does not align with the new picklist constraints.
Mapping custom Lead fields requires compatible target data types on Account, Contact, or Opportunity records. Furthermore, modifying a custom field's data type from Text to Picklist presents data loss risks if existing text data does not match the newly defined picklist values.

Step-by-Step Solution

1
Analyze Lead custom field mapping mechanics during lead conversion.
Lead conversion requires mapped fields on target objects (Account, Contact, Opportunity) to share compatible data types (e.g., Text to Text, Picklist to Picklist). Roll-Up Summary fields and unmapped fields cannot receive lead conversion data automatically.
Salesforce enforces field compatibility to maintain data integrity during record creation upon conversion.
2
Evaluate data type conversion risks when altering existing custom fields.
Converting a field from a flexible type (Text) to a structured type (Picklist) carries data loss risks if existing text values are not included in the picklist value set.
Salesforce warns administrators of potential data loss whenever changing data types to less permissive structures.
3
Identify correct operational statements matching Salesforce field rules.
Mapping compatible fields across objects and acknowledging data loss when modifying field data types are correct statements.
These rules reflect Salesforce core administration standards for field management and lead processing.

Key Concept

Custom Field Data Types and Lead Field Mapping Rules
Rate this question

Topics

Custom Fields and Data Types

More questions from this topic