A Salesforce administrator at an agricultural technology company is designing a custom data model. The management team requests a relationship between the standard Contract object and a new custom object named Crop_Inspection__c. The requirement specifies that Crop_Inspection__c must serve as the master object and Contract must serve as the detail object so that inspection records directly control contract access and lifecycle. Which statement correctly explains why this configuration cannot be implemented in Salesforce?
- ARoll-up summary fields can only be created on parent objects connected via a Lookup relationship rather than a Master-Detail relationship.
- Standard objects cannot be placed on the detail side of a Master-Detail relationship with a custom object.Cevap
- CDeleting a detail record in a Master-Detail relationship automatically causes the associated master record to be permanently deleted.
- DDefining a Master-Detail relationship requires configuring available picklist values under Record Type assignments prior to relationship creation.
Cevap
Standard objects cannot be placed on the detail side of a Master-Detail relationship with a custom object.
In Salesforce, standard objects cannot be on the detail side of a Master-Detail relationship with a custom object. While standard objects can act as the master in a Master-Detail relationship with custom objects, they cannot inherit ownership and security from a custom object as a detail record.
Adım Adım Çözüm
Anahtar Kavram
Standard and Custom Object Master-Detail Limitations