A Salesforce administrator at a logistics company wants to create an aggregate calculation on the custom Equipment__c object to display the total maintenance cost of all associated Work_Order__c records. Currently, Work_Order__c is linked to Equipment__c via a Lookup relationship. Which two statements describe the configurations or behavior required when creating a native Roll-Up Summary field for this scenario? (Select 2)
- The existing Lookup relationship must be converted to a Master-Detail relationship before a native Roll-Up Summary field can be created on Equipment__c.Answer
- BA native Roll-Up Summary field can be directly created on Equipment__c using the existing Lookup relationship by enabling cross-object calculations.
- Converting to a Master-Detail relationship causes all associated Work_Order__c records to be automatically deleted if their parent Equipment__c record is deleted.Answer
- DDeleting an Equipment__c master record retains associated Work_Order__c records as unparented standalone records.
Answer
The existing Lookup relationship must be converted to a Master-Detail relationship before a native Roll-Up Summary field can be created, and converting to a Master-Detail relationship causes associated detail records to be automatically deleted if the master record is deleted.
Native Roll-Up Summary fields are supported strictly on the master object within Master-Detail relationships, which requires converting the current Lookup relationship. Additionally, converting to a Master-Detail relationship implies cascading deletion, where deleting a master record automatically removes linked detail records.
Step-by-Step Solution
Key Concept
Roll-Up Summary Field Prerequisites and Master-Detail Deletion Behavior