A Salesforce Administrator is designing a custom data model to manage resource allocations. A custom object named Resource_Assignment__c serves as a junction object connecting the Project__c object and the Consultant__c object. The business requirement dictates that summary reporting of total allocated hours must be displayed directly on the Project__c record, and managers must be able to move an existing assignment record from one project to another when staffing shifts occur. Which two configuration choices or system behaviors must the administrator take into account for this data model? (Select 2 answers)
- The relationship between Resource_Assignment__c and Project__c must be a Master-Detail relationship to support Roll-Up Summary fields on Project__c.Cevap
- The Master-Detail relationship field referencing Project__c must have the 'Allow reparenting' setting enabled to permit reassigning records to a different project.Cevap
- CA Roll-Up Summary field can be configured on Project__c using a standard Lookup relationship field on Resource_Assignment__c.
- DDeleting a Project__c record will leave associated Resource_Assignment__c records intact, automatically converting their parent relationship into a blank value.
Cevap
The data model requires establishing a Master-Detail relationship to support Roll-Up Summary fields on the parent object, and the 'Allow reparenting' checkbox must be explicitly selected on the relationship field definition to allow shifting assignments between parent records.
Native Roll-Up Summary fields on custom parent objects require a Master-Detail relationship with the child object. Furthermore, because Master-Detail child records cannot be reparented by default, enabling the 'Allow reparenting' setting on the custom field definition is necessary to fulfill the requirement of moving assignment records between projects.
Adım Adım Çözüm
Anahtar Kavram
Master-Detail Relationship Capabilities and Reparenting Rules