Question

Difficulty: MediumCustom Fields and Data Types

A Salesforce administrator at a solar energy equipment manufacturer is configuring custom fields on custom objects tracking installation projects. The administrator must also plan for field data type conversions and lead mapping settings. Which two statements correctly describe Salesforce custom field capabilities and data type behaviors? (Select 2 answers.)

  1. Converting a custom Text Area (Long) field to a standard Text field truncates existing data if record values exceed 255 characters.Answer
  2. B
    Roll-up summary fields can be created on a parent object to aggregate numeric data from child records connected through a standard Lookup relationship.
  3. Converting a custom field from Number to Text preserves existing numeric data without loss of information.Answer
  4. D
    Newly created picklist values on an object are automatically assigned and enabled across all existing Record Types without manual configuration.
  5. E
    Custom Lead fields can be mapped to any standard or custom field on Accounts, Contacts, or Opportunities during lead conversion regardless of target field data type compatibility.

Answer

Converting a custom Text Area (Long) field to a standard Text field truncates data exceeding 255 characters, and converting a custom field from Number to Text preserves existing numeric data.
Converting a Text Area (Long) field to a standard Text field limits character capacity to 255 characters, causing longer entries to be truncated. Converting a Number field to a Text field preserves existing numeric entries as text characters without data loss.

Step-by-Step Solution

1
Analyze field data type conversion rules in Salesforce.
Changing from Text Area (Long) to standard Text reduces maximum length to 255 characters, truncating longer values. Converting Number to Text safely retains digits as string characters.
Salesforce enforces data length caps on standard Text fields and allows non-destructive conversion from Number to Text.
2
Evaluate relationship types, record types, and lead mapping rules against the distractors.
Roll-up summary fields require Master-Detail relationships. Picklist values must be assigned per Record Type. Lead conversion mapping requires matching/compatible field data types.
Salesforce architecture restricts roll-ups on lookups, mandates picklist assignment per record type, and requires compatible data types for lead field mapping.

Key Concept

Custom Field Data Type Behavior and Conversion Rules
Rate this question