An administrator at a cloud software company manages a custom parent object, Software_License__c, and a custom child object, User_Assignment__c, which are currently linked by a Lookup relationship. The business requests a real-time summary field on Software_License__c to display the total count of related User_Assignment__c records. When attempting to create a Roll-Up Summary field on Software_License__c, the administrator notices that the Roll-Up Summary field type option is grayed out and unavailable. Which configuration change must the administrator make to enable native Roll-Up Summary fields on Software_License__c?
- Convert the Lookup relationship field on User_Assignment__c to a Master-Detail relationship after ensuring all existing child records have a populated lookup field value.Cevap
- BCreate a cross-object formula field on Software_License__c that uses the COUNT() function to aggregate related User_Assignment__c records.
- CChange the Organization-Wide Default (OWD) sharing setting on User_Assignment__c to Controlled by Parent to automatically enable roll-up capabilities.
- DBuild a validation rule on Software_License__c to calculate and enforce the count of related child records whenever a license is saved.
Cevap
Convert the Lookup relationship field on User_Assignment__c to a Master-Detail relationship after ensuring all existing child records have a populated lookup field value.
Native Salesforce Roll-Up Summary fields require a Master-Detail relationship between objects. To convert a Lookup relationship into a Master-Detail relationship, all existing child records must have a value populated in the lookup field.
Adım Adım Çözüm
Anahtar Kavram
Master-Detail Relationship Requirement for Roll-Up Summary Fields