A Salesforce Administrator at a software-as-a-service (SaaS) platform needs to display the total number of active software licenses from related custom Subscription records directly on the parent Account record. The Subscription object currently has a Lookup relationship to Account. When attempting to create a Roll-Up Summary field on Account, the administrator notices the field type option is disabled. Which TWO configuration steps or requirements must the administrator address to successfully create the Roll-Up Summary field?
- Convert the existing Lookup relationship on the Subscription object to a Master-Detail relationship before creating the Roll-Up Summary field on Account.Answer
- Ensure that every existing Subscription record has a populated Account lookup field value prior to converting the relationship.Answer
- CCreate a cross-object formula field on the Account object to aggregate and count the related Subscription records across the lookup relationship.
- DChange the Organization-Wide Default (OWD) sharing setting on the Subscription object to Controlled by Parent to automatically enable roll-up capabilities.
Answer
The administrator must ensure all existing Subscription records have populated Account values and convert the Lookup relationship to a Master-Detail relationship.
In Salesforce, Roll-Up Summary fields are exclusively supported on the parent object of a Master-Detail relationship. Therefore, the existing Lookup relationship must first be converted to a Master-Detail relationship. Additionally, Salesforce enforces that a Lookup relationship can only be converted to a Master-Detail relationship if every existing child record has a non-null parent lookup value populated.
Step-by-Step Solution
Key Concept
Master-Detail Relationship Requirement for Roll-Up Summary Fields