Universal Containers has a well-defined role hierarchy in Salesforce where everyone is assigned to an
appropriate node. The accounts within their instance are categorized by their demography.
An individual sales rep should be able to view all accounts that they own. In addition, sales reps should be
able to see any accounts where the value of the account demography matches the demography defined on
their user record. A user could have more than one demography defined on their user record.
To meet this requirement, the CRM Analytics consultant has set up a security predicate of the existing
'Account' dataset as follows:This, however, does not seem to be working as expected.
What is causing the issue?
A company used Einstein Analytics to create two datasets:
1. "Opportunity With Account- dataset, which contains data from the Opportunity standard object augmented
by the Account data.
2. "Case with Account" dataset. which contains data from the Case standard object augmented by the Account
data.
The company wants to build a lens showing the total number of Opportunities and Cases per Account. How
can a consultant help them build this lens
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?
Cloud Kicks' Salesforce org has multiple currencies enabled. This company's business intelligence team uses
CRM Analytics to build a dataflow/recipe that creates a dataset, "OpportunityDataSet", which is populated
with data extracted from Opportunity. One of the extracted fields is the standard field, Amount.
Which currency will the Amount values be shown in "OpportunityDataSet"?
Universal Containers has a well-defined role hierarchy in Salesforce where everyone is assigned to an
appropriate node. The accounts within their instance are categorized by their demography.
An individual sales rep should be able to view all accounts that they own. In addition, sales reps should be
able to see any accounts where the value of the account demography matches the demography defined on
their user record. A user could have more than one demography defined on their user record.
To meet this requirement, the CRM Analytics consultant has set up a security predicate of the existing
'Account' dataset as follows:This, however, does not seem to be working as expected.
What is causing the issue?