Examkin

Question

Difficulty: HardStandard and Custom Object Management

An administrator at a renewable energy firm is building an inspection tracking architecture using a custom object named Solar_Inspection__c, which links to a parent custom object named Solar_Site__c. The business requirement demands calculating the aggregate total count of inspections directly on the Solar_Site__c record. However, when the administrator attempts to create a new field on Solar_Site__c, the Roll-Up Summary field type option is greyed out and unavailable. Which scenario explains why this field type is unavailable, and what prerequisite step is required to enable it?

  1. The relationship between Solar_Inspection__c and Solar_Site__c is currently configured as a Lookup relationship; the administrator must convert it to a Master-Detail relationship after ensuring all Solar_Inspection__c records have a populated lookup value.Answer
  2. B
    The relationship between Solar_Inspection__c and Solar_Site__c is a Lookup relationship, which supports Roll-Up Summary fields only after enabling Chatter Feed Tracking on both standard and custom objects.
  3. C
    The child object Solar_Inspection__c has deleted records residing in the Recycle Bin from a previous cascade deletion, which temporarily locks schema modifications on the master object until purged.
  4. D
    The Roll-Up Summary field type must first be explicitly assigned to the active Record Type picklist settings on the parent object before it can be selected in Object Manager.

Answer

The relationship between Solar_Inspection__c and Solar_Site__c is currently configured as a Lookup relationship; the administrator must convert it to a Master-Detail relationship after ensuring all Solar_Inspection__c records have a populated lookup value.
In Salesforce Core Administration, declarative Roll-Up Summary fields are exclusively available on the master object of a Master-Detail relationship. When a Lookup relationship is used, the system grey-outs the Roll-Up Summary option. To convert a Lookup relationship to a Master-Detail relationship, all existing child records must have a value in the lookup field.

Step-by-Step Solution

1
Identify the relationship type between the child object (Solar_Inspection__c) and the parent object (Solar_Site__c).
Determine that Roll-Up Summary fields are strictly limited to the parent/master side of a Master-Detail relationship.
Salesforce standard functionality prohibits Roll-Up Summary fields across standard Lookup relationships without custom code or declarative automation tools.
2
Verify data completeness across existing child records.
Ensure that every existing Solar_Inspection__c record contains a valid, non-null reference to a Solar_Site__c record.
Converting a Lookup field to a Master-Detail relationship will fail if any existing child record has a blank parent lookup field, as Master-Detail relationships require mandatory parent linkage.
3
Convert the relationship field type in Object Manager and create the Roll-Up Summary field on Solar_Site__c.
The Roll-Up Summary field type becomes available for selection on the master object once the relationship is Master-Detail.
Master-Detail relationships enforce tight coupling and data integrity required for real-time declarative aggregation calculations.

Key Concept

Roll-Up Summary Field Eligibility and Relationship Conversion Prerequisites
Rate this question

Topics

Standard and Custom Object Management

More questions from this topic