A logistics company tracks equipment servicing using a custom object named Maintenance_Log__c. An administrator is tasked with summarizing total maintenance counts on the standard Asset object and ensuring that deleting an Asset automatically removes all associated Maintenance_Log__c records. However, several Maintenance_Log__c records currently exist in the org without an assigned Asset. Which TWO steps must the administrator take to successfully implement this requirement?
- Populate the Asset lookup field on all existing Maintenance_Log__c records prior to converting the relationship to a Master-Detail relationship.Answer
- Create Roll-Up Summary fields on the standard Asset object after establishing the Master-Detail relationship.Answer
- CCreate a Roll-Up Summary field directly on the Asset object while keeping the existing Lookup relationship intact.
- DConfigure an automated deletion flow because child records remain active in the database by default when a master record is deleted in a Master-Detail relationship.
Answer
The administrator must populate the Asset reference on all existing Maintenance_Log__c records before converting the Lookup relationship to a Master-Detail relationship, and then create Roll-Up Summary fields on the Asset object.
To achieve automatic cascading deletion and native roll-up summary capabilities on the parent Asset object, a Master-Detail relationship is required. Converting an existing Lookup field to a Master-Detail field requires that every existing child record has a parent value populated. Once converted, Roll-Up Summary fields can be configured on the Asset object.
Step-by-Step Solution
Key Concept
Master-Detail Relationship Conversion Rules & Roll-Up Summary Requirements
Estimated Time:2m 0s