Universal Containers has a dashboard for sales managers that want to visualize their win rate.
Which chart type should the consultant use to keep track of targets?
The CRM Analytics consultant at Cloud Kicks (CK) notices that a specific dashboard is showing a different date and time from their locale. Upon investigating, they find that the recipe and datasetswere created from a locale with a PST time zone while CK is in the CET time zone.
What led to this problem?
Universal Containers uses CRM Analytics to build dashboards for different departments: Sales, Service, and Marketing. Users in the samedepartment 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.
consultant is tasked with creating an opportunity dataset for a new analytics app. One requirement is to make sure users only see the opportunities they have access to in Salesforce. Opportunity records are private but shared using the role hierarchy. The consultant runs
the sharing inheritance coverage assessment and finds that the VP of sales is not covered by the sharing inheritance. The consultant decides to proceed with using sharing inheritance for the dataset.
What else does the consultant need to do?
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 usesecurity 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.
Sanjay Shukla
8 days agoDuc Tran
20 days agoData Layer Martinez
1 month agoEinstein Discovery Brown
3 days agoSecurity Perez
25 days ago