An administrator at a global logistics firm is designing custom data tracking between a parent custom object named Project__c and a child custom object named Project_Task__c. Currently, Project_Task__c is linked to Project__c via a standard Lookup relationship. The business requires calculating the total estimated hours from all related tasks on the Project record, as well as displaying the Project's priority level on each child task record. Which two statements accurately describe the capabilities and configuration requirements for this scenario?
- Native roll-up summary fields on Project__c require converting the relationship field on Project_Task__c from a Lookup to a Master-Detail relationship.Cevap
- Cross-object formula fields on Project_Task__c can reference fields from the parent Project__c record using the existing Lookup relationship.Cevap
- CNative roll-up summary fields can be created on Project__c over the Lookup relationship if the Lookup field is configured as required on Project_Task__c.
- DDeleting a Project__c record will automatically cascade and delete all associated Project_Task__c records while linked via the standard Lookup relationship.
Cevap
To aggregate child task hours onto the Project object using native roll-up summary fields, the relationship must be converted from a Lookup to a Master-Detail relationship. Furthermore, cross-object formulas on child records can access parent fields regardless of whether the relationship is Lookup or Master-Detail.
Native roll-up summary fields in Salesforce strictly require a Master-Detail relationship between the parent (master) and child (detail) objects. Therefore, converting the existing Lookup relationship to a Master-Detail relationship is necessary to summarize child task hours on the Project object natively. Additionally, cross-object formula fields on child records are capable of referencing fields from parent records across both Lookup and Master-Detail relationships.
Adım Adım Çözüm
Anahtar Kavram
Roll-Up Summary and Cross-Object Formula Relationship Constraints