A CRM Analytics administrator is working on deploying a dashboard and a dataset from a developer sandbox to a full sandbox. They have deployed the dataset via change set and manually copy-pasted the dashboard JSON into the target org. However, they notice that the conditional formatting and the widget-specific number formats have been lost in the target environment.
What is causing this issue?
When deploying a dataset and dashboard between environments in CRM Analytics, it's essential to include the Extended Metadata (XMD) file, which controls aspects such as conditional formatting and number formatting. In this case, the administrator manually copied the dashboard JSON but did not deploy the Analytics Dataset XMD, which leads to the loss of conditional formatting and widget-specific number formats in the target environment. Including the XMD ensures that all formatting and metadata are transferred correctly.
Cloud Kicks has informed CRM Analytics developers that they have two scenarios with restricted row-level security.
The parameters being:
1. Non-CXOs and VPs working in EMEA can have access to EMEA records only.
2. CXOs and VPs should have access to all data irrespective of the region (APAC, EMEA, etc.).
Which sharing method works for this scenario?
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.
CRM Analytics users at Cloud Kicks are granted access to an app with specific dashboards. When trying to download a specific widget, they are unable to do so.
In CRM Analytics, even if users are granted access to view an app and its dashboards, their ability to download data is controlled by permissions assigned via permission sets. Specifically, users need the 'Download Data' permission to download data from widgets or dashboards. If this permission is missing from their permission set, they will be unable to download the specific widget, even though they can view the data.
A CRM Analytics consultant is adding direct data into an existing recipe. When trying to click on the input node, data preview is taking a long time to show any results.
How should the consultant resolve this?
The CRM Analytics consultant at Cloud Kicks is asked to make sure the data on the CRM Analytics dashboard be as real-time as possible.
It was agreed to set the sync refresh time to 5 minutes for one of the local connections. The org has a CRM Analytics Plus license but users are noticing that the earliest available time is 1 hour. The minutes option is not visible to the user.
What is causing the issue?
In the scenario where Cloud Kicks wants to set the sync refresh time to 5 minutes but finds that the minimum available time is 1 hour, the limitation is due to the licensing and feature availability in CRM Analytics Plus. Here's the detailed explanation:
License Restrictions: The CRM Analytics Plus license typically sets the minimum refresh interval at 1 hour. This is a built-in restriction that reflects the platform's capabilities and resource allocation norms.
Platform Capabilities: While more frequent refreshes would be ideal for achieving near-real-time data synchronization, such capabilities might require additional customization or advanced setup, potentially involving higher tiers of service or additional Salesforce products.
Operational Considerations: Frequent data refreshes, especially in shorter intervals like 5 minutes, can significantly impact system performance and resource utilization. Therefore, such options are generally restricted or managed tightly within Salesforce environments.
This understanding aligns with Salesforce's documentation and product specifications, which outline what features and capabilities are available under different licensing agreements.
Britt
1 months agoJohnetta
3 months agoBarney
4 months agoCandra
4 months agoMerilyn
5 months agoRory
5 months agoRachael
6 months agoSamira
6 months agoDenny
6 months agoWilda
7 months agoEllsworth
7 months agoArthur
8 months agoZachary
8 months agoDaren
8 months agoKayleigh
8 months agoJesusita
9 months agoMalcolm
9 months agoCecilia
9 months agoTamar
9 months agoAlton
11 months agoBoris
11 months agoAlise
12 months agoDerrick
12 months agoTarra
1 years ago