CRM Analytics team plans to enable data sync.
Which limit specific to data syne should the team consider before enabling the feature because it may impact existing jobs?
In CRM Analytics, when planning to enable data sync, one of the critical considerations is the limit on the number of objects that can be enabled for data sync. This limit is essential because it determines how many different Salesforce objects (like Accounts, Opportunities, etc.) can be synchronized concurrently. Exceeding this limit could impact the performance of existing sync jobs or prevent new sync jobs from being configured.
Key points to consider include:
Performance Impact: Syncing too many objects simultaneously can lead to increased load times and potential delays in data availability, impacting users' ability to access up-to-date information.
Resource Allocation: CRM Analytics allocates resources based on the number of objects being synchronized, and there are practical limits to these resources to ensure stable and efficient operation.
For a more detailed understanding and to manage these limits effectively, Salesforce provides documentation and guidelines within the CRM Analytics resources, which can be further explored in the Trailhead modules specifically focusing on data management and synchronization practices.
A CRM Analytics consultant is updating an existing recipe.
They are looking to add a few additional fields onto the Account dataset. One of the fields to be added is a multi-select picklist field that needs to be shown as text on the dashboard.
What should the consultant do to accomplish this?
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.
Loreta
17 days agoStevie
2 months agoBritt
3 months agoJohnetta
4 months agoBarney
5 months agoCandra
6 months agoMerilyn
6 months agoRory
7 months agoRachael
8 months agoSamira
8 months agoDenny
8 months agoWilda
9 months agoEllsworth
9 months agoArthur
9 months agoZachary
10 months agoDaren
10 months agoKayleigh
10 months agoJesusita
10 months agoMalcolm
11 months agoCecilia
11 months agoTamar
11 months agoAlton
1 years agoBoris
1 years agoAlise
1 years agoDerrick
1 years agoTarra
1 years ago