Question

Difficulty: HardCustom Fields and Data Types

An administrator at a maritime logistics company needs to calculate the total freight weight on a custom parent object, Shipment__c, by summarizing weight values from child records on a custom object named Container_Package__c. The Container_Package__c object currently references Shipment__c through a Lookup relationship. When attempting to create a Roll-Up Summary field on Shipment__c, the administrator discovers that Container_Package__c is not available in the list of summarized objects. Which administrative action must be taken to enable the Roll-Up Summary field on the Shipment__c object?

  1. Convert the existing Lookup relationship field on Container_Package__c to a Master-Detail relationship after verifying that all existing Container_Package__c records have a populated Shipment__c value.Answer
  2. B
    Create the Roll-Up Summary field directly on the Container_Package__c child object while maintaining the existing Lookup relationship to Shipment__c.
  3. C
    Configure custom Lead field mapping settings to map the Container_Package__c weight field to the parent Shipment__c object.
  4. D
    Modify the active Record Type configuration on Container_Package__c to assign the Shipment__c picklist values prior to field creation.

Answer

The administrator must convert the existing Lookup relationship field on Container_Package__c to a Master-Detail relationship after ensuring all existing Container_Package__c records have a populated Shipment__c value.
In Salesforce, Roll-Up Summary fields can only be defined on the master object of a Master-Detail relationship to aggregate data from child detail records. Because the existing relationship is a Lookup relationship, the child object will not appear as an option in the Roll-Up Summary field setup wizard. Converting the Lookup field on the child object to a Master-Detail relationship makes the parent object the master, allowing roll-up summaries to be created. For this conversion to succeed, every child record must currently have a populated lookup value.

Step-by-Step Solution

1
Identify why Container_Package__c is unavailable in the Roll-Up Summary wizard.
Roll-Up Summary fields are natively supported only on the master object in a Master-Detail relationship, not on objects linked via Lookup relationships.
Salesforce requires a Master-Detail relationship to enforce strict parent-child data architecture necessary for automated roll-up calculations.
2
Determine the required data clean-up prerequisite for relationship conversion.
Ensure that every record on the child object (Container_Package__c) has a valid value populated in the existing Lookup field.
A Master-Detail relationship requires the master reference field to be mandatory on all child records.
3
Convert the relationship and create the field.
Convert the Lookup field on Container_Package__c to Master-Detail, then create the Roll-Up Summary field on Shipment__c.
Once converted, Shipment__c becomes the master object and gains the capability to aggregate child field values.

Key Concept

Roll-Up Summary Prerequisites and Relationship Type Conversion
Estimated Time:2m 0s
Rate this question