Ursa Major Solar tracks custom Service_Contract__c records that serve as parent records to custom Equipment_Maintenance__c records using a Master-Detail relationship. The administrator also maintains a standard Lookup relationship between Service_Contract__c and the object. The business requires reporting aggregated maintenance costs on the service contract as well as displaying asset warranty dates dynamically. Which two field configuration rules and system behaviors must the administrator take into account when setting up Roll-Up Summary and Cross-Object Formula fields?
- Roll-Up Summary fields can only aggregate data from records linked via a Master-Detail relationship and cannot summarize fields on objects connected solely through a Lookup relationship.Answer
- BMaking a Lookup relationship field required on the child object enables Roll-Up Summary field creation on the parent object.
- A Roll-Up Summary field cannot summarize a custom formula field on a child object if that formula field references values from another related object.Answer
- DDeleting a child detail record in a Master-Detail relationship preserves the parent record's Roll-Up Summary value until the record is permanently removed from the Recycle Bin.
Answer
Roll-Up Summary fields require a Master-Detail relationship and cannot summarize child formula fields that contain cross-object references.
Native Roll-Up Summary fields in Salesforce strictly require a Master-Detail relationship between parent and child objects. Furthermore, Salesforce imposes limits on summarizing formula fields on child objects: if a child field relies on a cross-object formula spanning another relationship, it cannot be referenced as the target of a Roll-Up Summary field.
Step-by-Step Solution
Key Concept
Roll-Up Summary Field Capabilities and Formula Restrictions