Examkin

Question

Difficulty: HardObject Relationships (Lookup, Master-Detail, Many-to-Many)

A company tracks software feature requests using a custom child object named Enhancement_Request__c, which currently connects to a custom parent object, Product_Module__c, through a Lookup relationship. The product management team requires real-time count metrics on Product_Module__c to track total feature requests. When the Salesforce Administrator attempts to convert the existing Lookup relationship field into a Master-Detail relationship field to build a Roll-Up Summary field, Setup returns an error preventing the schema change. What is the root cause of this error, and how should the administrator resolve it?

  1. Existing child records contain null values in the Lookup field; the administrator must populate the lookup field on all existing Enhancement_Request__c records before converting the data type.Answer
  2. B
    Roll-Up Summary fields are unsupported on custom objects converted from lookup fields; the administrator must delete the lookup field and create a new Master-Detail field from scratch.
  3. C
    Child records will automatically be permanently deleted if the parent object OWD is altered; the administrator must export and delete all child records prior to changing the relationship type.
  4. D
    The child object's Organization-Wide Default setting is set to Private; the administrator must change the Organization-Wide Default of Enhancement_Request__c to Controlled by Parent prior to field conversion.

Answer

Populate the Lookup field on all existing child records with a valid parent record reference, then convert the lookup field to a master-detail relationship.
To convert an existing Lookup relationship to a Master-Detail relationship, every existing record on the child object must contain a populated value in the lookup field. Because Master-Detail relationships strictly enforce parent record reference requirements (detail records cannot exist without a master), Salesforce prevents field conversion if any child record has a blank/null lookup value. Populating these records allows the conversion to complete successfully, which in turn enables the creation of Roll-Up Summary fields on the parent object.

Step-by-Step Solution

1
Identify the mandatory requirements for converting a Lookup field to a Master-Detail field in Salesforce.
Recognize that Master-Detail relationships require every detail record to be linked to a master record (the relationship field cannot be blank).
Salesforce enforces database integrity for master-detail relationships, ensuring no orphan detail records exist.
2
Analyze why changing the field data type failed during Setup configuration.
Determine that existing child records in the custom object contain null (blank) values in the existing lookup field.
If any child record lacks a value in the lookup field, Salesforce blocks the data type conversion to prevent master-detail integrity violations.
3
Formulate the correct administrative resolution strategy.
Populate valid parent record references across all existing child records via Data Loader or mass update, then execute the field type conversion in Object Manager.
Once all child records possess a non-null relationship value, the system permits conversion from Lookup to Master-Detail, subsequently allowing Roll-Up Summary field creation.

Key Concept

Converting Lookup Relationships to Master-Detail Relationships
Estimated Time:2m 0s
Rate this question

Topics

Object Relationships (Lookup, Master-Detail, Many-to-Many)

More questions from this topic