An administrator at a global freight routing company is configuring custom fields on a custom object named Freight_Order__c to track package metrics, delivery parameters, and relationship metadata.
Which two factors should the administrator consider when configuring custom field data types and relationship settings on this object? (Select TWO)
- Changing a custom field type from Number to Text preserves existing data values on records while allowing future entries to contain alphanumeric characters.Answer
- Converting a Master-Detail relationship to a Lookup relationship requires deleting any existing Roll-Up Summary fields on the master object first.Answer
- CRoll-Up Summary fields can be created on the parent object even when the parent and child objects are linked by a standard Lookup relationship.
- DCustom fields created on the Lead object can be mapped directly to custom fields on Task and Event activity records during lead conversion.
- EAdding a new value to a custom picklist field automatically updates all existing Record Types on the object to include the new value.
Answer
The administrator must consider that converting a Number field to a Text field preserves existing data while accepting future alphanumeric values, and converting a Master-Detail relationship to a Lookup relationship requires first deleting any Roll-Up Summary fields on the master object.
Converting a custom field from Number to Text preserves existing field data while allowing alphanumeric input for future records. Furthermore, converting a Master-Detail relationship to a Lookup relationship is permitted only after any existing Roll-Up Summary fields on the master object referencing the detail object have been deleted.
Step-by-Step Solution
Key Concept
Custom Field Data Type Conversion and Relationship Capabilities