An administrator at a logistics company manages a custom data model where individual Package__c records are linked to a parent Delivery_Manifest__c object via a standard Lookup relationship. Management requests a field on Delivery_Manifest__c that automatically calculates the cumulative weight of all associated packages. When attempting to create a field on Delivery_Manifest__c, the Roll-Up Summary field type is disabled. Which configuration change must the administrator make to fulfill this requirement?
- Convert the existing Lookup field on Package__c into a Master-Detail relationship after ensuring all existing Package__c records have the Delivery_Manifest__c lookup field populated.Cevap
- BCreate the Roll-Up Summary field on the child Package__c object and configure it to aggregate values onto the parent Delivery_Manifest__c record.
- CChange the Organization-Wide Default (OWD) sharing setting of Package__c to Controlled by Parent to enable Roll-Up Summary fields on the Lookup relationship.
- DDelete the existing Package__c records, create a Master-Detail relationship on Delivery_Manifest__c pointing to Package__c, and re-import the package data.
Cevap
Convert the existing Lookup field on Package__c into a Master-Detail relationship after ensuring all existing Package__c records have the Delivery_Manifest__c lookup field populated.
Declarative Roll-Up Summary fields require a Master-Detail relationship where the summarizing object acts as the master. Converting the Lookup relationship on the child object to a Master-Detail relationship enables Roll-Up Summary fields on the parent object, provided all existing child records contain populated parent lookup values prior to conversion.
Adım Adım Çözüm
Anahtar Kavram
Roll-Up Summary Field Capabilities and Relationship Conversion Prerequisites