A System Administrator at a corporate training firm needs to track aggregate metrics on the custom parent object Training_Course__c based on related child Course_Registration__c records. Currently, Course_Registration__c is linked to Training_Course__c via a standard Lookup relationship. The administrator wants to display the total number of enrolled participants and the maximum fee paid directly on the Training_Course__c record using standard platform declarative tools.
Which two considerations or constraints must the administrator keep in mind when designing this solution?
- Standard Roll-Up Summary fields cannot be created on Training_Course__c while the objects are linked via a Lookup relationship.Answer
- Converting the Lookup relationship to a Master-Detail relationship requires that all existing Course_Registration__c records have a populated Training_Course__c lookup field.Answer
- CA cross-object formula field on Training_Course__c can be used to aggregate and sum numeric values from all related child Course_Registration__c records.
- DDeleting a Training_Course__c record will automatically delete associated Course_Registration__c records while the relationship remains a standard Lookup relationship.
Answer
Standard Roll-Up Summary fields require a Master-Detail relationship structure and cannot be created over a Lookup relationship. Additionally, converting a Lookup relationship to a Master-Detail relationship requires that all existing child records have a populated lookup field value.
Standard Roll-Up Summary fields require a Master-Detail relationship. Converting an existing Lookup relationship to a Master-Detail relationship mandates that every existing child record has a populated value in the lookup field.
Step-by-Step Solution
Key Concept
Roll-up summary relationship prerequisites and conversion considerations