# Active Filters in Widgets

> Dashboard and widget filters restrict the data displayed in the dashboard's widgets.

*Source: https://docs.sisense.com/main/SisenseLinux/active-filters-in-widgets.htm*

---

Last updated: June 11, 2026

|  |  |
| --- | --- |
| [Tier](https://www.sisense.com/pricing/#pricing) | [Deployment](https://docs.sisense.com/main/SisenseLinux/introduction-to-sisense-cloud-managed-services.md#ComparisonofManagedCloudandSelfHosted) |
| Launch     Grow    Enterprise | Cloud     On-Prem |

Dashboard and widget filters restrict the data displayed in the dashboard's widgets. Widgets use filters at two levels, to determine:

- Which of the filters to apply in order to **calculate** measures
- Which of the filters to apply in order to determine what to **display** in the widget

For each dimension attribute, the widget first calculates the measures, and then applies the relevant dashboard and/or widget filters to display the resulting data in the widget.

## Calculation Hierarchy

When calculating measures, the widget applies the following hierarchy:

1. Filters on measures - All filters that require a sub-query in order to calculate them. For widget calculations, any top raking filter, regardless of whether it is on a measure or a dimension, is considered to be a filter on a measure.
2. Widget filters
3. Dashboard filters

**Note:**

A filter on a dimension (a filter within a measured value - see [Measured Values](https://docs.sisense.com/main/SisenseLinux/measured-values.md)) is a regular filter. That is, it filters out values on one dimension, without requiring a measure to calculate it.

## Presentation Hierarchy

When calculating what to display in the widget, the widget applies the following hierarchy:

1. Widget filters
2. Dashboard filters

**Note:**

- A filter on a dimension attribute on a widget overrides a dashboard filter on the same dimension attribute.
- Filters on different levels on date are considered to be different dimension attributes. That is, they do not clash with each other and therefore no precedence needs to be determined.
- Dashboard filters on columns that are not relevant to a widget are ignored.