Dashboard Filters
Dashboard Filters are runtime filters applied to a Salesforce Lightning dashboard that scope every component whose underlying report contains the filtered field.
Definition
Dashboard Filters are runtime filters applied to a Salesforce Lightning dashboard that scope every component whose underlying report contains the filtered field. Each dashboard supports up to three filters, each with up to 50 filter values. A viewer picks values from the filter dropdown in the dashboard header and the components re-render against the filtered slice without anyone editing the source reports.
Dashboard Filters work above the report layer, applied after the source query but before component rendering. A component whose source report does not have the filter field simply ignores the filter; it does not error out or hide. This is what makes the same dashboard usable across regions, account segments, or product lines. One dashboard, three filters, fifty values each, and a sales operations team that does not have to clone the dashboard nine times.
How Dashboard Filters cut one dashboard into the slices each stakeholder actually needs
The three-filter cap and why it forces design discipline
Three filters per dashboard is a hard limit. Most enterprise dashboards run out of room when leadership wants Region, Segment, Product Family, Time Period, and Channel all filterable at once. The pattern that works is picking the three highest-leverage cross-cuts (typically Region, Segment, and Time Period) and letting users open a different dashboard for the rarer slices. Pushing past three with workarounds (filter components, embedded report filters, multiple dashboards) usually loses the simplicity that made the filter strategy valuable.
Filter values are configured per-dashboard, not from picklist metadata
Adding a new value to the underlying picklist field does not auto-add it to the dashboard filter. Each value has to be entered manually in the filter configuration. This is the most common Dashboard Filter support ticket: marketing adds a new Industry to the picklist, the dashboard filter still shows the old eight industries, and the new one is silently excluded. Build a quarterly audit of dashboard filter values against the source field picklist values.
How filters interact with components that lack the filter field
A component whose source report does not include the filter field continues to show all data, unfiltered. This is intentional; it lets you mix corporate-level metric components (total revenue, total pipeline) with region-specific charts on the same dashboard. The corporate metrics do not change when the viewer picks Region = West, because the source report has no Region field at all. Spot this by clicking the gear on each component and reading the data source; mismatched filter behavior usually traces here.
Component-level filters override dashboard filters
Each component can carry its own filter set, applied on top of the dashboard filter. The component-level filter narrows further; if the dashboard filter says Region = West and a component filter says Stage = Closed Won, the component shows Region=West AND Stage=Closed Won. Use this for side-by-side comparisons: a Pipeline component with no extra filter next to a Closed-Won component with Stage=Closed Won, both responding to the dashboard-level Region filter.
Filter operators and the picklist constraint
Dashboard filters support equals, not equals, less than, greater than, contains, starts with, and a handful of date operators. The values for an equals filter must be enumerated in the filter configuration; you cannot type a free-form value at view time. For dynamic ranges (last 30 days, current quarter), use the relative date operators rather than typed-in date strings. Date operators understand FY (fiscal year), FQ, and TODAY tokens.
Dashboard Filters versus URL parameters and embedded filters
Three filtering layers can apply at once. Dashboard filters (the UI dropdown) operate at the dashboard level. Source-report filters (defined on the underlying report) operate before the dashboard ever sees the data. URL parameters can pass filter values directly via the dashboard URL, which is how managers bookmark "their" filtered view. All three layers AND together. A field filtered by all three with conflicting values returns no rows; users see empty components and assume the dashboard is broken when it is actually doing exactly what was asked.
Lightning Dashboard filters versus CRM Analytics dashboards
Lightning Dashboard filters cap at three. CRM Analytics dashboards support unlimited filters, including range sliders, multi-select dropdowns, and cascading filter behavior. If three filters is not enough and the dashboard is core to the business, the question is usually whether to migrate the use case to CRM Analytics rather than to hack around the Lightning limit. CRM Analytics carries a license cost; the trade-off is real.
Adding and configuring Dashboard Filters
Dashboard Filters are configured in the dashboard editor under the gear icon. Set them up after the components are placed so you can see immediately which components respond to which filter.
- Open the dashboard in edit mode
Dashboards tab, find the dashboard, click Edit. The editor shows the grid of components and a header with the gear icon. Filters live under Edit Dashboard Properties or the dedicated + Filter button in the header.
- Add the first filter
Click + Filter in the dashboard header. Pick the field. The filter form lets you label the filter (the dropdown label viewers see), pick an operator, and define up to 50 filter values with friendly display names. Filter values can include All as a default value.
- Define filter values
For picklist filters, enter each value that should be selectable. For numeric or date filters, define range buckets (Q1 covers Jan 1 to Mar 31, etc). Each value gets a display label shown in the dropdown plus the underlying filter logic.
- Save and test against each component
Save the dashboard. Pick a value from the filter dropdown. Watch which components update; components built on reports without the filter field stay static. Mismatches are usually because the filter field is named differently on different source reports (Account.Industry vs Account.Industry__c).
- Set a default filter value
Edit the filter and choose a default. The default applies when a viewer opens the dashboard without picking a filter explicitly. Useful for region-specific dashboards where the implicit "everyone" view is misleading.
Any field on the source reports that the filter should target. Must exist on the report; a field on the underlying object that is not on the report does not work.
Equals, not equals, less than, greater than, contains, starts with, and date-specific operators (within last N days, FY, FQ, TODAY).
Up to 50 enumerated values per filter, each with a display label and underlying filter logic. Multi-select is supported on equals filters.
The value applied when a viewer opens the dashboard. Defaults to All if not set.
- Three-filter cap is hard. Plan which cross-cuts are most valuable; do not promise stakeholders a fourth filter.
- Filter picklist values do not auto-sync from the source field metadata. Adding a new Industry to the field requires editing the dashboard filter.
- Components on reports that lack the filter field do not filter. This is intentional, but confuses viewers expecting all components to respond uniformly.
- URL parameters, source-report filters, and dashboard filters AND together. Conflicting filters return empty components; check all three layers when debugging.
- Date filters use the relative-date operators (FY, FQ, TODAY). Typed-in date strings do not work; bookmark URLs with literal dates break in the next month.
Trust & references
Cross-checked against the following references.
- Filter Dashboards in LightningSalesforce Help
- Add a Dashboard FilterSalesforce Help
Straight from the source - Salesforce's reference material on Dashboard Filters.
- Dashboard Filter Considerations and LimitsSalesforce Help
- Filter a Dashboard with a URL ParameterSalesforce Help
Hands-on resources to go deeper on Dashboard Filters.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What do Dashboard Filters let viewers do?
Q2. How many Dashboard Filters can you add to a single dashboard?
Q3. What's the advantage of Dashboard Filters over building separate dashboards?
Discussion
Loading discussion…