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?
A versioning feature allows CRM Analytics users to be added as Publishers and make changes separately
while a ‘Live’ version is still being usedby other users. Once the changes are complete, the user can then set
their updated version as the Live version.
Which CRM Analytics item is this leveraged for?
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?