Examkin

Question

Difficulty: MediumDashboard Design, Components, and Dynamic Filters

A Salesforce Administrator is configuring a sales operations dashboard in Lightning Experience that incorporates components derived from both Account and Opportunity report types. The management team wants to filter the dashboard by Region and requires that managers see only the data they have permission to access. Which two considerations must the administrator keep in mind when configuring the dashboard components and dynamic filters? (Select 2)

  1. A maximum of 3 filters can be added to a single dashboard, and fields must be mapped explicitly if the source report types do not share identical field names.Answer
  2. Configuring the dashboard to run as the logged-in user allows viewers to see data based on their own access permissions without granting access to restricted records.Answer
  3. C
    Setting the dashboard running user to a dynamic view automatically overrides Organization-Wide Defaults (OWD) so managers can access underlying regional data.
  4. D
    Creating a row-level formula inside the dashboard component settings is required to aggregate regional totals across distinct source report types.

Answer

The administrator must account for the limit of 3 dashboard filters with explicit field mapping across different report types, and understand that running dynamic dashboards as the logged-in user respects individual user record permissions.
The correct statements recognize that Salesforce imposes a hard limit of 3 filters per dashboard requiring explicit field mapping when source reports differ, and that running dynamic dashboards as the logged-in user strictly enforces existing record-level access control.

Step-by-Step Solution

1
Evaluate dashboard filter limits and mapping rules for multiple report types.
Salesforce limits dashboards to 3 filters, and components using different report types require explicit field mapping for the filter to work across all components.
Different source reports may reference distinct objects (Accounts vs. Opportunities), so explicit field mapping tells the dashboard engine which field to filter on for each component.
2
Analyze security and dynamic running user settings.
Dynamic dashboards running as the logged-in user restrict displayed data strictly to what each user has permissions to view.
Dynamic dashboards adapt visibility to the viewing user's security context without altering OWD or sharing access.

Key Concept

Dashboard Filters and Dynamic Dashboard Security
Rate this question

Topics

Dashboard Design, Components, and Dynamic Filters

More questions from this topic