Last Attempt Tableau-CRM-and-Einstein-Discovery-Consultant Questions

When deploying a dashboard such as SalesPerformance_1 from a sandbox to production in Salesforce Tableau CRM using a package, the correct metadata reference in the XML file is typically formatted with a suffix that identifies the type of component. For dashboards in Tableau CRM, the suffix "waveDashboard" is used, hence the correct reference would be "SalesPerformance_1 waveDashboard."

Two benefits of designing using the "Progressive Disclosure" principle are:

• A: Improved ease of use for end users. By only displaying essential information initially and allowing users to access more detailed data as needed, dashboards become less cluttered and more user-friendly.
• D: Better dashboard performance. This design principle can also lead to better performance as less data is processed and rendered initially, speeding up load times and responsiveness.

To allow users who belong to an account team to see all the opportunities associated with that account in Einstein Analytics, the recommended actions are:

• Apply sharing inheritance: This ensures that the security settings and visibility of the Account object are inherited by related records, like Opportunities, making it easier to manage access based on existing Salesforce CRM security models.
• In the dataflow, extract the AccountTeamMember object and augment it with the Opportunity object using 'AccountId' as the join field: This method allows the consultant to directly link team members to the accounts and their opportunities, ensuring that visibility in Einstein Analytics mirrors the CRM's team-based permissions.

These approaches leverage Salesforce's inherent security features and ensure data visibility is consistent with user roles and relationships defined in the CRM system.