Free Access Salesforce Tableau-CRM-and-Einstein-Discovery-Consultant New Release

To build a lens showing the total number of Opportunities and Cases per Account using two separate datasets, the consultant can:

• D: Use a SAQL query to group and join the "OpportunityWithAccount" and "CaseWithAccount" datasets then generate the results. This method involves writing a SAQL query that groups the data by Account and aggregates the number of Opportunities and Cases, providing a unified view of the data across both datasets.

In Tableau CRM (formerly Einstein Analytics), you can restrict access to data at the row level using security predicates. Security predicates are filter expressions added to datasets that dynamically restrict data access based on user attributes or record specifics. This method allows administrators to enforce data security policies directly within the dataset, ensuring that users only see data relevant and permitted to them, without altering the underlying data structure like removing rows manually or adding flags. Reference: https://help.salesforce.com/s/articleView?id=sf.bi_security_predicates.htm &type=5

Predicate is a name for a filter condition that defines row-level access to records in a dataset Example: "rowLevelSecurityFilter":"'AccountOwner' == \"$User.Name\""

The edgemart transformation, which grants a dataflow access to an existing, registered dataset, is specified in the Dataflow Editor. This tool within Salesforce Tableau CRM allows users to define and manipulate dataflow transformations, integrating various datasets into the analytical environment.

When planning to enable data sync (replication) in Einstein Analytics, two specific limits that should be considered are:

• C: Maximum number of objects that can be enabled for data sync (replication). This limit affects how many Salesforce objects can be set up for regular synchronization without creating new dataflows.
• D: Timeout for ELT (Extract, Load, Transform) jobs that are scheduled but not yet executed. This limit impacts the maximum allowable time that data sync jobs can remain in the queue before execution, which is critical for maintaining up-to-date data.