Examkin

Question

Difficulty: MediumCustom Fields and Data Types

A Salesforce administrator at a biomedical equipment manufacturer is updating field configurations on a custom object named Medical_Device__c. The administrator needs to convert an existing custom field, Calibration_Interval_Days__c, from a Number data type to a Picklist data type to enforce standardized values. Furthermore, the administrator needs to calculate the total repair expenditure by summarizing maintenance costs from a related custom object, Maintenance_Log__c, which is currently connected to Medical_Device__c through a Lookup relationship.

Which two statements accurately describe the system impacts and requirements of implementing these changes? (Select TWO.)

  1. Converting the custom field from Number to Picklist can result in data loss if existing numerical values do not correspond to the newly defined picklist values.Answer
  2. Roll-up summary fields cannot be created on Medical_Device__c to aggregate repair costs because Maintenance_Log__c is connected using a Lookup relationship.Answer
  3. C
    Converting a custom field to a Picklist automatically assigns all newly created picklist values to all existing record types on the Medical_Device__c object.
  4. D
    Converting the custom field to a Picklist automatically enables field mapping to standard Lead conversion fields without additional setup.
  5. E
    Converting the relationship to Master-Detail ensures that deleting a child Maintenance_Log__c record will automatically delete the parent Medical_Device__c record.

Answer

Converting a Number field to a Picklist field can cause data loss if existing numerical data does not match newly defined picklist entries, and Roll-up Summary fields cannot be created over Lookup relationships because they strictly require a Master-Detail relationship.
Data type conversion from Number to Picklist can cause data loss if values do not match defined picklist entries. Additionally, roll-up summary fields require a Master-Detail relationship and cannot be created on parent objects linked via Lookup relationships.

Step-by-Step Solution

1
Analyze the implications of data type conversion from Number to Picklist.
Identified that converting data types from numeric formats to picklists poses a risk of data loss for any existing field values that do not align with the new picklist entries.
Salesforce warns of data loss when changing custom field types to Picklist from numeric or text data types.
2
Evaluate the relationship requirement for Roll-up Summary fields.
Determined that roll-up summary capability is unavailable on parent objects connected via a Lookup relationship.
Roll-up summary fields require a Master-Detail relationship between parent and child objects to aggregate values automatically.

Key Concept

Custom Field Data Type Conversion Risks and Roll-up Summary Relationship Requirements
Rate this question

Topics

Custom Fields and Data Types

More questions from this topic