Explanation:

When uploading data via the External Data API, a JSON metadata file defines the field data types (dimension, measure, etc.).

If the JSON metadata file is not provided, CRM Analytics defaults all fields to dimension type, which prevents mathematical aggregations.

Option B (double quotes) usually affects string parsing but does not cause all fields to be treated as dimensions.

Option C is about transforming data at the source, but the key issue is field type definition during ingestion.

Therefore, to enable numeric operations, the consultant must upload a proper JSON metadata file alongside the CSV, specifying field types correctly.

Explanation:

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.

Explanation:

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 Widgetsand 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.

Explanation:

The Enable Expand or Collapse feature allows users to expand or collapse groups in a compare table, making it much easier to navigate tables with multiple groupings and detailed data.

This interactive feature improves usability by letting users focus on summary or detailed views as needed.

Option A (using SAQL) is more complex and not necessary just for enabling expand/collapse functionality.

Option C (scrolling to the end) is not user-friendly and does not improve navigation.

Explanation:

When you install a Sales Analytics templated app, Salesforce automatically creates a bundle of data assets—recipes, dataflows, connectors, Einstein Discovery models, and prediction definitions—that are interdependent. To ensure these assets refresh in the correct sequence, you should schedule the entire app rather than individual components.

Here’s how to do it:

Go to Setup → search for App Install History.
Locate the installed templated app (e.g., Sales Analytics).
Click the dropdown next to the app and select Schedule.
Choose 6:00 AM EST as the refresh time and save.

This ensures that all assets refresh in the correct order, maintaining data integrity and minimizing manual coordination.

Why not A or B?
Option A: Manually scheduling each asset is time-consuming and error-prone. It also risks running assets out of order.
Option B: This only covers recipes and dataflows, but not connectors, Einstein Discovery models, or prediction definitions.