The CRM Analytics consultant at Universal Containers (UC) has set up data sync for the Salesforce Opportunity object with the Amount currency field added. This is being used in multiple datasets and dashboards, as UC is a multi-currency organization.The currency used in Salesforce records is set up in GBP but the data on the dashboard is converting to USD. Conversion logic is not set up on any of the recipes.Why is the currency converting?
Answer(s): C
In Salesforce CRM Analytics, when dealing with multi-currency environments, the system relies on the organization's corporate currency setting for reporting, unless explicitly overridden. In this case, even though the Opportunity data is stored in GBP in Salesforce, the dashboards are showing USD because the corporate currency for the org is set to USD. This behavior is expected unless currency conversion logic is implemented in the datasets or recipes. The corporate currency serves as the default for currency fields in datasets and dashboards unless configured otherwise. This can be confirmed under the "Manage Currencies" settings in Salesforce.
The currency handling rules in CRM Analytics, including how the corporate currency affects reporting, are detailed in Salesforce documentation on multi-currency organizations and the Einstein Discovery training materials.
Universal Containers' sales team is looking to build a dashboard that shows the total revenue from their top 10 accounts (based on revenue) and make it dynamic with the filters of the dashboard.Which action is required to accomplish this?
Answer(s): A
To create a dashboard showing the top 10 accounts by revenue dynamically, the best approach is to create a query that sorts the accounts in descending order by revenue and limits the results to the top 10. This query can then be used as the data source for the widget, ensuring that it dynamically adjusts based on the filters applied to the dashboard. This method efficiently handles the task because sorting by revenue and limiting the results to 10 ensures that only the top accounts are displayed, and it remains dynamic with dashboard filters.
This approach is covered in the Building Lenses, Dashboards, and Apps in CRM Analytics module, where techniques for creating dynamic queries are discussed.
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(s): 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.
Recipe runtime limits and considerations for scheduling refreshes are discussed in the CRM Analytics documentation related to recipes and dataflow optimizations.
Universal Containers plans to upload target data from an external tool to CRM Analytics so it can calculate the sales team target attainments.The target data changes every month, so the datasets need to be updated on a monthly basis. The target data is a CSV file that contains the Salesforce ID of the sales rep, the target amount, and the month of the target. For each sales rep, the file contains a target for every month of the current year as well as all previous years.Based on this information, which operation should a consultant use with the Analytics External Data API to upload the file?
For uploading target data that changes on a monthly basis and includes historical data (previous years' targets), the appropriate operation is "Overwrite." This ensures that each time the CSV file is uploaded, the existing data in the dataset is replaced with the new data. This is critical because the target data includes both current and historical data, and using "Overwrite" will update the entire dataset while maintaining historical accuracy."Append" would add new data without replacing the old records, leading to duplication, and "Update" is not suitable for completely replacing data in this context.
The usage of the "Overwrite" operation for updating datasets with changing data is covered in the Analytics External Data API documentation, as well as in the Wave Analytics Explorer module.
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.
Detailed information on XMD files and their role in formatting is covered in the CRM Analytics deployment and customization documentation.
Post your Comments and Discuss Salesforce ANC-301 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the ANC-301 content, but please register or login to continue.