Addressing Performance Issues with Universal Containers' Account Sharing Rules | Certified Sales Cloud Consultant
Question
Universal Containers has automated the process of creating new account records in Salesforce. All account records created through this process are owned by a generic user. There are now two million account records that have been created in this manner. Universal Containers is now seeing performance issues when it makes any changes to account sharing rules.
What can Universal Containers do to address the issue without changing its integration?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.A
In order to address the performance issues faced by Universal Containers when making changes to account sharing rules without changing its integration, several options are provided as answers. Let's go through each option and explain its relevance:
A. Ensure that the generic user has NOT been assigned to a role. Assigning a user to a role affects their access to records based on the role hierarchy. If the generic user is assigned to a role, it means they have implicit access to all the records owned by users below them in the hierarchy. This can lead to a large number of account records being accessible to the generic user, which might impact performance when making changes to sharing rules. Therefore, ensuring that the generic user is not assigned to a role could help mitigate the performance issues.
B. Ensure that the generic user has the Modify All Data permission. The Modify All Data permission is a powerful permission that grants a user the ability to modify all records in the organization, regardless of ownership or sharing settings. By assigning this permission to the generic user, they would have unrestricted access to modify account records. While this option may provide a solution to the performance issues, it is not recommended from a security standpoint unless absolutely necessary.
C. Contact Salesforce support to add an index to the account object. Indexes in databases are used to improve the speed of data retrieval and queries. By adding an index to the account object, Salesforce can optimize the way it retrieves and processes account records, which could help improve performance when making changes to sharing rules. Contacting Salesforce support for assistance in adding an index is a valid approach to address the performance issues.
D. Set the organization-wide defaults for accounts to public read/write. Organization-wide defaults (OWDs) define the default access level for records across the entire organization. By setting the OWD for accounts to public read/write, it means that all users in the organization would have read and write access to all account records. While this option may potentially resolve the performance issues, it also significantly compromises data security, as it allows unrestricted access to account records for all users.
To summarize, the most suitable option to address the performance issues without compromising security would be to contact Salesforce support (option C) and request assistance in adding an index to the account object. This approach optimizes the data retrieval and processing, specifically for account records, and can potentially improve the performance when making changes to sharing rules.
