A manager at Cloud Kicks wants to separate and analyze accounts based on numeric information of its opportunity records. The data includes things like amount, quantity of products, contacts, and
quotes.
How should the CRM Analytics consultant accomplish this?
Universal Containers' CRM Analytics team is building a dashboard with two widgets, and the queries use different datasets.
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 "Query_pie_3" and grouped by the dimension "Type"
The team wants any selection in the List widget to filter the Donut chart and vice vers
a. Users should be able to choose more than one Type (multi-selection).
What is the recommended way to accomplish the required filtering?
A CRM Analytics consultant has been asked to bring data from an external database as well as five external Salesforce environments into CRM Analytics. Twenty-five objects have been enabled from the local Salesforce connector.
The requirements are:
* 10 objects should be enabled from an external database
* 12 objects each from three of the external Salesforce environments
* 15 objects each from the remaining two external Salesforce environments
The consultant estimates each connector will, per object, bring between 1,000 and 1 million rows of data.
Which limit will be exceeded?
In evaluating the scenario presented where multiple external sources and objects are being integrated into CRM Analytics, we need to consider the total number of enabled objects across all connections. Here's a breakdown:
10 objects from an external database
12 objects each from three external Salesforce environments, totaling 36 objects
15 objects each from two external Salesforce environments, totaling 30 objects
25 objects already enabled from the local Salesforce connector
This brings us to a total of 101 objects enabled, which may exceed typical limits on the number of objects that can be enabled in a CRM Analytics environment, depending on the specific Salesforce licensing and platform limits.
After the initial creation of a model, the first model insight explains
93% of the variation of the outcome variable. This is unusually high.
What is the most likely reason for this?
What is a benefit of introducing a second local connector?
Introducing a second local connector in CRM Analytics can improve performance by enabling more granular control over data syncs. By having a separate connector, different datasets or recipes can be synchronized independently based on specific refresh needs, reducing load and improving overall performance. This approach helps optimize data flow operations, especially in large-scale deployments with varying data refresh requirements.
