Universal Containers asks a CRM Analytics consultant to review the performance of its local data sync.
After removing unused objects and fields from connected data, what else should the consultant do to improve performance of the data sync?
To improve the performance of local data sync in Universal Containers, evaluating the connection mode for each connected object is a practical approach. Here's the rationale:
Optimization of Resources: Different connection modes (e.g., Full Sync, Incremental Sync) use different amounts of resources. Choosing the right mode for each object based on how frequently its data changes can optimize the sync process and reduce load times.
Efficient Data Handling: By tailoring the connection mode to the needs of specific data objects, the overall efficiency of the data sync process is improved, leading to faster refresh rates and more timely data availability.
Cost and Performance Balance: Evaluating and selecting the appropriate connection mode can also help balance performance needs with cost constraints, as some modes may consume more compute resources than others.
A versioning feature allows CRM Analytics users to be added as Publishers and make changes separately while a 'Live' version is still being used by other users. Once the changes are complete, the user can then set their updated version as the Live version.
Which CRM Analytics item is this leveraged for?
In CRM Analytics, the versioning feature described is typically leveraged for Apps. This feature allows:
Parallel Development: Users can work on changes in a separate version without affecting the live version being accessed by others.
Controlled Publishing: Once changes are finalized, the user can then promote their version to be the new live version, ensuring seamless updates without disrupting ongoing usage.
Collaborative Workflows: Facilitates teamwork by allowing multiple users to propose and test changes in a controlled environment before making those changes live.
This approach ensures that CRM Analytics apps remain dynamic and can evolve over time while maintaining stability and continuity for end-users.
A consultant has been asked to build and embed a dashboard in a Lightning page. Users should only be able to change the dashboard contrast and open Analytics Studio from the header of
the dashboard.
How should the consultant achieve this?
Universal Containers uses CRM Analytics to build dashboards for different departments: Sales, Service, and Marketing. Users in the same department have the same role and need to have access to the same dashboards. Dashboards for different departments use some common datasets with the same row-level security.
How should a CRM Analytics consultant address this need?
For managing access to department-specific dashboards while leveraging common datasets, the best approach involves the use of apps and permission sets. Here's why:
App Segregation: Creating a separate app for each department (Sales, Service, Marketing) allows for tailored dashboards and datasets to be grouped by department, facilitating easier management and navigation.
Shared Common Datasets: Placing common datasets in a shared app ensures that all departments can access necessary data without duplication, maintaining consistency and reducing storage requirements.
Use of Permission Sets: Leveraging permission sets to control access to these apps is a flexible and scalable approach. Permission sets can be finely tuned to grant or restrict access based on user roles within the organization, and they can be easily adjusted as roles or organizational structures change.
This structure not only ensures data security and appropriate access but also enhances the efficiency of managing CRM Analytics resources across different departments.
A consultant runs the sharing inheritance coverage assessment for the Opportunity object and finds that some records exceed 400 sharing descriptors.
What should the consultant do?
When a record exceeds 400 sharing descriptors, it can cause performance issues or sharing rule complications in CRM Analytics. In such cases, the recommended solution is to use security predicates, which allow fine-tuned control over which data is visible to users based on their sharing rules and permissions. Security predicates reduce the number of sharing descriptors by enforcing security at the dataset level rather than relying solely on record-sharing mechanisms.
Increasing the sharing descriptor limit is not an available option, and Salesforce Support does not typically increase this limit, making the use of security predicates the best approach.
