Question

Difficulty: MediumDashboard Design, Components, and Dynamic Filters

A Salesforce Administrator at an automotive dealership group is configuring a central sales and service performance dashboard in Lightning Experience. The dashboard incorporates components based on both Lead and Service Appointment custom reports. To allow regional managers to refine the dashboard metrics by geographic territory and timeframe, the administrator plans to add dynamic dashboard filters. Which two requirements and capabilities must the administrator consider when implementing these dashboard filters? (Select 2)

  1. A maximum of 3 filters can be added to a single Lightning dashboard.Answer
  2. B
    Applying a dashboard filter automatically expands a user's record-level access to match the running user's visibility for filtered components.
  3. Fields used for filtering must be explicitly mapped for each source report if the equivalent fields differ across objects.Answer
  4. D
    Source reports can evaluate row-level formulas as summary filters to bypass grouping requirements when adding chart components.

Answer

The correct requirements are that a maximum of 3 filters can be added to a single Lightning dashboard, and fields used for filtering must be explicitly mapped for each source report when the objects differ.
Salesforce enforces a standard limit of 3 dynamic filters per Lightning dashboard. Additionally, when dashboard components rely on source reports built from different objects, the administrator must map the filter to equivalent fields on each object so the filter applies correctly across all components.

Step-by-Step Solution

1
Identify system limits for Lightning dashboard filters
Confirm that Salesforce limits each dashboard to a maximum of 3 dashboard filters.
This is a hard platform governor limit for dashboard configuration.
2
Determine how dashboard filters operate across multi-object source reports
Recognize that field mapping is required when source reports draw from different objects (e.g., Leads vs. Service Appointments).
Each report component must know which specific field to filter on when a user selects a filter value.
3
Evaluate security and grouping constraints
Verify that dashboard filters respect existing security models and do not override source report grouping rules required for charts.
Filters only slice existing report data; they do not alter sharing rules or report structure prerequisites.

Key Concept

Lightning Dashboard Filters and Field Mapping
Rate this question