A Salesforce Administrator at a medical device manufacturing company needs to calculate and display the total number of completed service inspections on the custom parent object Medical_Device__c using data from the custom child object Inspection_Log__c. The two objects are currently connected via a Lookup relationship. When attempting to create a Roll-Up Summary field on Medical_Device__c, the Administrator finds the Roll-Up Summary field type disabled. Which two statements correctly explain this behavior or describe the required resolution steps? (Select 2 answers.)
- Roll-Up Summary fields are supported only on the master object of a Master-Detail relationship and cannot be created over a Lookup relationship.Cevap
- The Lookup field on Inspection_Log__c must be populated for all existing records before converting the relationship to Master-Detail.Cevap
- CChanging the Organization-Wide Default sharing setting of Inspection_Log__c to 'Controlled by Parent' automatically enables Roll-Up Summary field creation on Lookup relationships.
- DA cross-object formula field can be created on Medical_Device__c to dynamically sum values across multiple child Inspection_Log__c records.
Cevap
Roll-Up Summary fields require a Master-Detail relationship, and converting an existing Lookup relationship to Master-Detail requires that all child records have a populated lookup field value.
Native Salesforce Roll-Up Summary fields are exclusively available on the master object of a Master-Detail relationship. To enable this capability when objects are connected by a Lookup relationship, the Administrator must convert the Lookup field to a Master-Detail relationship field. A prerequisite for converting a Lookup field to Master-Detail is ensuring that every existing child record contains a value in the lookup field.
Adım Adım Çözüm
Anahtar Kavram
Roll-Up Summary Fields Relationship Requirements and Conversion Rules