Salesforce Sales Cloud Consultant Exam: Implementing Multi-Level Account Hierarchy | Recommended Solution

Implementing Multi-Level Account Hierarchy in Salesforce Sales Cloud: Best Recommendation

Question

A consultant is implementing a new Sales Cloud instance for Cloud Kicks (CK) that has a public sharing model for Accounts. Different sales reps own local Accounts that create a multi-level Account Hierarchy. CK needs to see the total number of closed won opportunities and the revenue value for all Accounts in the hierarchy when viewing a parent Account.

Which recommendation meets this requirement?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

B

To meet the requirement of displaying the total number of closed won opportunities and the revenue value for all accounts in the hierarchy when viewing a parent account, the most appropriate recommendation would be:

Option C: Use the View Account Hierarchy option and include a custom Roll-Up Summary field with the total value of won Opportunities in the displayed columns.

Here's a detailed explanation of why Option C is the best choice:

  1. Create a Roll-Up Summary field on the parent Account with the total value of won Opportunities from the child Accounts: This option involves creating a Roll-Up Summary field on the parent Account object, which calculates the sum of the won Opportunities from child Accounts. However, Roll-Up Summary fields are not supported across account hierarchies in Salesforce. They can only roll up data within the same object or to the parent in a master-detail relationship. Therefore, this option is not suitable for achieving the desired outcome.

  2. Configure an after-save Flow to update a custom field on the parent Account with the total value of won Opportunities from the child Accounts: This option suggests using an after-save Flow to update a custom field on the parent Account with the total value of won Opportunities from the child Accounts. While this approach is technically feasible, it may not be the most efficient solution. After-save Flows trigger on every save operation, which could result in unnecessary processing and increased resource consumption. Additionally, using Flows for this purpose adds complexity and requires extra maintenance. Therefore, this option is not the optimal choice.

  3. Use the View Account Hierarchy option and include a custom Roll-Up Summary field with the total value of won Opportunities in the displayed columns: This option provides the desired functionality by utilizing the built-in "View Account Hierarchy" feature in Salesforce. When viewing a parent Account, this feature displays a visual representation of the account hierarchy, including child Accounts. By including a custom Roll-Up Summary field in the displayed columns, you can show the total value of won Opportunities for all child Accounts. This allows Cloud Kicks to easily access the required information without the need for additional customization or complex workflows.

  4. Create a Workflow Rule to update the custom field on the parent Account with the total value of won Opportunities from the child Accounts: This option suggests using a Workflow Rule to update a custom field on the parent Account with the total value of won Opportunities from the child Accounts. However, similar to Option 2, this approach has limitations. Workflow Rules are not designed to perform calculations across multiple records or traverse hierarchical relationships. Therefore, this option would not be suitable for achieving the desired outcome.

In conclusion, Option C is the recommended approach as it leverages the existing "View Account Hierarchy" feature in Salesforce and includes a custom Roll-Up Summary field to display the total value of won Opportunities for all child Accounts in the hierarchy. This solution is efficient, requires no additional customization, and provides a straightforward way for Cloud Kicks to access the desired information.