What is causing the issue?

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 . The Sales Rep is not provided access permission on custom field Demographic__c on the User object.
B . The security predicate needs to be updated as ‘Ownerld’ == "sUser.id” || ‘Demography’ = "$User.Demographic__c’.
C . The Analytics Security User is not provided access permission on custom field Demographic_c on the User object.

View Answer

Answer: A

Explanation:

The issue with the security predicate not functioning as expected likely stems from a permissions issue related to the custom field Demographic__c on the User object. Here’s a detailed explanation: Field-Level Security: If the sales reps do not have access to the Demographic__c field, the security predicate which references this field cannot execute properly as the system cannot evaluate the predicate without accessing the field.

Permission Settings: Ensuring that the sales reps have the necessary permissions to view and use the Demographic__c field is crucial for the security predicate to function correctly.

Data Visibility: The security model in CRM Analytics relies heavily on the underlying data permissions in Salesforce. If these permissions are not correctly configured, the expected data visibility through CRM Analytics will not be achieved.