The sales team at Cloud Kicks is requesting that datasets for their dashboards be refreshed every hour. The CRM Analytics consultant investigates if this is possible and finds that the dashboards use five datasets created from two recipes. The first recipe takes 43 minutes to run and the second recipe takes 25 minutes to run.
Which consideration should the consultant keep in mind?
Answer : B
In CRM Analytics, recipes are used to prepare and combine data for datasets. The total duration of the recipe runtime is an important consideration when scheduling dataset refreshes. In this case, the combined runtime for both recipes (43 minutes + 25 minutes = 68 minutes) exceeds 1 hour. Since dataset refreshes cannot be scheduled more frequently than the total recipe runtime, it would be impossible to refresh the datasets every hour. This limitation must be considered when managing dataset refresh schedules.
A CRM Analytics consultant at Cloud Kicks wants to create a new dashboard that uses custom GeoJSON to display data; however, they are unable to upload the file via the user interface (UI).
Which action should the consultant take?
Answer : C
If a consultant at Cloud Kicks needs to use custom GeoJSON files for dashboard visualization and cannot upload the file via the CRM Analytics user interface (UI), the recommended action is to use the API for this purpose. Here's why this approach is suggested:
Functionality Limitation in UI: Currently, the CRM Analytics UI does not support direct uploads of GeoJSON files, which necessitates an alternative method.
API Flexibility: The API provides a more flexible route for uploading custom GeoJSON files, allowing consultants to integrate more complex or larger datasets that are not supported through standard UI functionalities.
Customization and Control: Using the API also offers greater control over how GeoJSON data is handled, processed, and utilized within CRM Analytics, catering to more advanced customization needs.
This method ensures that the consultant can fully utilize CRM Analytics' capabilities for creating highly customized geographic visualizations, thereby enhancing the analytical value of the dashboards.
Which statement best describes how to ensure CRM Analytics dashboards are easily used across both desktop and mobile devices?
Answer : C
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.
Universal Containers (UC) is using CRM Analytics to create two datasets.
* Dataset A: Contains a list of activities with an "activityID" dimension and a "userID" dimension
* Dataset B: Contains a list of users with a "userID" dimension
UC wants to delete all activities from Dataset A related to users in Dataset B.
How should the CRM Analytics consultant help UC achieve this?
Answer : A
In CRM Analytics, when dealing with two datasets, such as Dataset A (activities) and Dataset B (users), and you want to delete records from Dataset A based on the users listed in Dataset B, you would typically use a combination of a join and filter transformation in a recipe. The join transformation allows you to combine data from both datasets based on the shared userID dimension, and the filter transformation would then be used to delete or exclude any activities from Dataset A that are associated with the users from Dataset B. This approach ensures that only relevant activities remain in Dataset A after filtering out the unwanted ones. Reference: CRM Analytics Recipes: Join and Filter Transformations
Universal Containers' CRM Analytics team is building a dashboard with two widgets.
1. List widget associated to the query "Type_2" and grouped by the dimension "Type" (multi-selection)
2. Donut chart widget associated to the query "Step_pie_3" and grouped by the dimension "Type"
The team wants to use bindings/interactions so any selection in the List widget will filter the Donut chart. The queries use different datasets,
and users should be able to choose more than one Type (multi-selection).
What is the right syntax for the binding/interaction?
A)

B)

C)

Answer : A
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.
Universal Containers (UC) uses a Microsoft Azure SQL Data Warehouse to gather information about sales reps' objectives. UC wants to use CRM Analytics to gain insights from this data and automatically load it into a CRM Analytics dataset daily. The data also needs to be transformed and merged with data from the company's org.
Which CRM Analytics user interface features should be used to complete these requirements?
Answer : B
CRM Analytics provides out-of-the-box connectors for integrating external data sources like Microsoft Azure SQL Data Warehouse. To meet the requirement of daily automated data loading, the Microsoft Azure SQL Data Warehouse Connector can be used to pull data into CRM Analytics. Once the data is imported, dataflows or recipes can be used to transform and merge this data with the organization's Salesforce data. Recipes allow for merging datasets and applying any necessary transformations, ensuring the data from Azure is combined and transformed appropriately before analysis. Reference: CRM Analytics Connectors and Dataflows
CRM Analytics uses permissions of the Integration User to extract data from Salesforce objects and fields when a dataflow/recipe job runs.
Why should a consultant be cautious while syncing objects and fields containing sensitive data?
Answer : C