To ensure that CRM Analytics dashboards are optimally usable on both desktop and mobile devices,

creating multiple layouts tailored to each device type is crucial. Here's why Option C is the best

approach:

Device-Specific Layouts: By creating specific layouts for each device type, you ensure that the

dashboard contents are presented in a manner best suited to the screen size and interaction model

of the device.

Layout Selectors: These are used to automatically display the appropriate layout based on the device

accessing the dashboard, enhancing user experience without manual intervention.

Widget Customization: Resizing or hiding certain widgets for specific device layouts ensures that the

dashboard remains clean, uncluttered, and easy to navigate, regardless of the device used.

To meet the requirement of training some users to create dashboards while giving another team

access to use (but not modify) those dashboards, the best approach is to configure a permission set

license assignment with two different levels of access. You can assign specific permissions for

dashboard creation to one group of users and viewing permissions to the other. This ensures the

appropriate level of access based on the role without the need for duplicating permission sets or

licenses unnecessarily.

Reference: The role of permission sets and permission set licenses in managing different levels of

access is outlined in Salesforce CRM Analytics user management and security documentation

The Repeater Widget in CRM Analytics allows dynamic updates to be reflected on the dashboard

automatically as data flows are updated. This means that as new account managers join or existing

account managers change roles, the data in the widget will automatically reflect the latest

information without manual updates. This is the most efficient way to keep the dashboard up-to-

date with the current list of account managers.

Reference: The functionality of Repeater Widgets and their ability to dynamically update based on

live data is covered in the Wave Analytics Explorer documentation, particularly when dealing with

team structures and dynamic datasets.

When embedding a CRM Analytics dashboard in a Lightning page using a CRM Analytics Dashboard

Component, you must configure the component’s visibility settings correctly to ensure that all

relevant users have access. In this case, the issue arises because the system administrator can see

the dashboard, but the contract manager cannot. The most likely cause is that the consultant has set

the component visibility to display only for system administrators, which would prevent the contract

manager from seeing the content. To resolve this issue, the consultant must modify the component

visibility settings to include both the system administrator and contract manager profiles.

Reference: CRM Analytics and Lightning Components

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.

Reference: Security predicates and their use to optimize data visibility and sharing within CRM

Analytics are explained in the CRM Analytics documentation related to security and performance.

:

:

For the given requirement where a selection in a list widget needs to filter data displayed on a donut

chart, and considering the list allows for multi-selection of the 'Type', the correct binding/interaction

would be to use a syntax that captures the multi-select aspect and passes it appropriately. The right

syntax, as indicated in Option A, looks like this:

"{{column(Type_2.selection, [\"Type\"]).asObject()}}"

This syntax ensures:

Multi-selection: The column() function in combination with .asObject() ensures that multiple

selected values from the 'Type_2' query can be passed as an object, which the donut chart can utilize

to filter its content.

Correct Data Type Handling: By using .asObject(), the binding ensures the data passed between

widgets maintains the correct structure expected by the CRM Analytics dashboard, thereby ensuring

accurate filtering.

For Cloud Kicks' requirements regarding access to data based on roles and geographic regions, the

most efficient and scalable approach is to implement row-level security using fields on the user

record, like Department or Region. Here's the rationale for choosing this approach:

Scalability and Maintenance: By applying security rules based on user record fields, Cloud Kicks can

manage access dynamically without needing to maintain multiple dashboards or datasets. This

reduces administrative overhead and simplifies updates as roles or regional structures change.

Flexibility: Using a field on the user record to control access allows for easy expansion or modification

of security policies as new regions or roles are added.

Simplicity: This method ensures a clear and straightforward security model that can be easily audited

and understood by administrators and compliance teams.

: