A Salesforce Administrator at a consulting firm is designing data tracking capabilities between a custom parent object, Project__c, and a custom child object, Project_Task__c. The two objects are currently linked using a standard Lookup relationship. The administrator needs to display the total estimated hours from related Project_Task__c records on the Project__c record, as well as display parent Project__c budget details on each Project_Task__c record. Which two statements accurately reflect the capabilities and limitations of Roll-Up Summary and Formula fields in this setup? (Select 2 answers)
- A Roll-Up Summary field cannot be created on Project__c unless the relationship to Project_Task__c is converted from a Lookup to a Master-Detail relationship.Answer
- Cross-object formula fields on Project_Task__c can reference fields on Project__c regardless of whether the relationship is a Lookup or a Master-Detail relationship.Answer
- CRoll-Up Summary fields can aggregate values across a Lookup relationship as long as the lookup field on Project_Task__c is configured as a required field.
- DConverting the Lookup relationship to a Master-Detail relationship ensures that deleting a parent Project__c record leaves related Project_Task__c records intact without deletion.
Answer
Roll-Up Summary fields require a Master-Detail relationship to function on the parent object, whereas cross-object formula fields can span across both Lookup and Master-Detail relationships.
Standard Salesforce Roll-Up Summary fields require a Master-Detail relationship on the parent object to aggregate child values (COUNT, SUM, MIN, MAX). In contrast, cross-object formula fields on child objects can freely reference fields from parent objects across both Lookup and Master-Detail relationships.
Step-by-Step Solution
Key Concept
Roll-Up Summary Relationship Requirements and Cross-Object Formula Capabilities