An administrator at an industrial equipment supplier manages a custom object named Equipment_Inspection__c that is linked to the standard Asset object through a Master-Detail relationship. The business operations team requests changing this Master-Detail relationship into a Lookup relationship so that inspection records can have independent record ownership and security control. However, when the administrator attempts to modify the relationship field type in Object Manager, Salesforce displays an error preventing the change. Which situation is preventing the administrator from converting the Master-Detail relationship to a Lookup relationship?
- The standard Asset object has a Roll-Up Summary field that calculates aggregate metrics from related Equipment_Inspection__c records.Answer
- BExisting Equipment_Inspection__c records in the organization do not have populated values in the Asset relationship field.
- CThe Equipment_Inspection__c custom object has multiple active Record Types with distinct picklist value assignments.
- DThe relationship field is currently included on a Dynamic Forms enabled page layout with conditional component visibility rules.
Answer
The conversion from a Master-Detail relationship to a Lookup relationship is blocked because the master Asset object contains a Roll-Up Summary field that references the child Equipment_Inspection__c object.
Salesforce prevents converting a Master-Detail relationship to a Lookup relationship if any Roll-Up Summary fields exist on the master object that aggregate data from the detail object. Because Roll-Up Summary fields are exclusively supported on Master-Detail relationships, those fields must be removed before the relationship type can be changed to Lookup.
Step-by-Step Solution
Key Concept
Relationship Field Type Conversions and Roll-Up Summary Dependencies