A Salesforce Administrator needs to aggregate financial metrics on a custom parent object, Hotel_Property__c, using values from child Guest_Reservation__c records. The requirement is to display the total revenue of completed stays directly on the Hotel_Property__c record.
Which two requirements or considerations apply when configuring a Roll-Up Summary field for this scenario?
- A Master-Detail relationship must exist between Hotel_Property__c and Guest_Reservation__c, with Hotel_Property__c designated as the master object.Answer
- All Roll-Up Summary fields on Hotel_Property__c that reference Guest_Reservation__c must be deleted before converting the relationship from Master-Detail to Lookup.Answer
- CStandard Roll-Up Summary fields can be created on Hotel_Property__c even if Guest_Reservation__c is connected via a standard Lookup relationship.
- DDeleting a Hotel_Property__c record will leave related Guest_Reservation__c records intact while clearing their relationship lookup fields.
Answer
The administrator must ensure a Master-Detail relationship exists with Hotel_Property__c as the master object, and must delete any existing Roll-Up Summary fields before converting the relationship to a Lookup relationship in the future.
Standard Roll-Up Summary fields are exclusively available on the master object of a Master-Detail relationship. Furthermore, Salesforce schema integrity rules mandate that any existing Roll-Up Summary fields referencing a detail object must be removed before converting that Master-Detail relationship into a Lookup relationship.
Step-by-Step Solution
Key Concept
Roll-Up Summary Field Capabilities and Relationship Constraints