# Applying global filters

Global filters apply consistent filtering across all tabs within a Vizpad. Any filter configured at the global level cascades to every chart and tab in the Vizpad, ensuring uniform data context across the entire dashboard.

1. In a Vizpad, click on the **Add Filter** button and the following menu will be displayed.

<figure><img src="https://content.gitbook.com/content/8GaK1h3pmgbR63x0ftET/blobs/jcL5SkHmXmBguBA3AAjF/image.png" alt="" width="208"><figcaption></figcaption></figure>

2. Click on the **Applied to** option to determine the charts for which you will apply the filter.

<figure><img src="https://content.gitbook.com/content/8GaK1h3pmgbR63x0ftET/blobs/nrLsNjYNcPcgbXLApyDD/image.png" alt="" width="210"><figcaption></figcaption></figure>

2. If you want to apply a global filter (for all charts in all tabs), then select **All charts in the Vizpad**. All subsequent filter configurations apply to every Vizpad tab.
3. If you want to apply filters all the charts in the current tab, then select All charts in the tab.
4. If you want to apply the filters only to specific charts, then select **Selected Charts in this tab**.

{% hint style="info" %}
Once you set up the filter to be applied, then the following panel appears along with checkboxes for each chart/table in the current tab.

<p align="center"><img src="https://content.gitbook.com/content/8GaK1h3pmgbR63x0ftET/blobs/zOvFues2PNNIuqtMYghJ/image.png" alt="" data-size="original"></p>

You can select the required charts and the count will be increased accordingly in the panel. **Select all** selects all the visuals in the tab, and the filter will be applied to the selected charts once you click on **Apply**.
{% endhint %}

5. If you want to apply filters to any date columns, then enable the Date filter toggle.

{% hint style="danger" %}
When **Date filter** toggle is disabled, only measures and dimensions will be displayed in the **Select Column** dropdown. If it is enabled, then only date columns will be displayed in the **Select Column** dropdown.
{% endhint %}

6. Once **All charts in the Vizpad** is selected, then the minimum and maximum range will be auto-selected. However, it overrides manual range modification so you can make necessary changes as required.
7. The auto-range will be selected as follows:
   1. **Measures**: Selects the minimum and maximum values of the measure.
   2. **Dimensions**: Defaults to `IN` (inclusion) operator.
   3. **Date columns:** Calculates `MIN(date_column)` to `MAX(date_column)` from entire dataset.

<figure><img src="https://content.gitbook.com/content/8GaK1h3pmgbR63x0ftET/blobs/sUvfNh9Eb8AR32wtNyM6/Frame%206369.png" alt="" width="375"><figcaption></figcaption></figure>

8. Enable the **Use Alignment Mapping** toggle if you want to refer only the mapped measures. This will be displayed only if **Date filter** is enabled.
9. Click on the **Select time period** field and the following window will be displayed. The available **Measure → Date** mappings for the Business View will be listed.
10. Choose the required time range from the available list.

<figure><img src="https://content.gitbook.com/content/8GaK1h3pmgbR63x0ftET/blobs/3v9PlioF1kwkTL3hzSf4/image.png" alt="" width="366"><figcaption></figcaption></figure>

11. Click on **Apply** to save the changes. The date filter will be applied to the selected chart(s).

{% hint style="warning" %}
To set up new **Measure → Date** mapping(s) or to edit the existing mappings, please check out this [page](https://help.tellius.com/data/preparing-your-business-views/mapping-measures-to-date-columns).
{% endhint %}

<figure><img src="https://content.gitbook.com/content/8GaK1h3pmgbR63x0ftET/blobs/W7chcovrm6BdxkqqFRxh/Frame%206367.png" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
Because you mapped **Sales, Quantity, Discount → Order\_Date** and chose **Last year** with **Date mapping** enabled, Tellius first kept only the rows whose **Order\_Date** fell in last year. Then it aggregated by **Category**.

\
Without mapping, the time filter could have hit a different date column or been applied across measures. Mapping forces the filter to use the correct date per metric, so your bars and lines are apples-to-apples for “last year.”
{% endhint %}

### Cascading filters in multi-fact Business Views

When your Business View spans multiple underlying fact tables, Vizpad filters (global and tab level filters) now behave more predictably by distinguishing between related and unrelated columns when cascading filter values.

**What cascading means:** Cascading filters automatically narrow the available values in one filter dropdown based on what you select in another. For example, if you select <mark style="color:$primary;">**Country = "United States"**</mark> in one filter, a <mark style="color:$primary;">**State**</mark> filter dropdown would cascade to show <mark style="color:$primary;">**only US states**</mark> rather than all states globally. This is helpful behavior when the two fields are genuinely related.

Now, Vizpad only cascades filter values when the columns are truly related, meaning they come from the same source dataset within the Business View. When columns come from different underlying datasets, their filter dropdowns remain independent of each other.

**Example:** Suppose your Vizpad has two filters: <mark style="color:blue;">**Region (from a geography table)**</mark> and <mark style="color:green;">**Brand (from a product table)**</mark>, and the Business View pulls data from multiple fact tables. Previously, selecting <mark style="color:blue;">**Region = "East"**</mark> might have incorrectly shrunk the <mark style="color:green;">**Brand**</mark> dropdown, even though <mark style="color:blue;">**Region**</mark> and <mark style="color:green;">**Brand**</mark> are unrelated fields from different source tables. Now, selecting <mark style="color:blue;">**Region = "East"**</mark> does not affect the <mark style="color:green;">**Brand**</mark> dropdown at all. However, filters like ***Country → State*** still cascade correctly because they come from the same underlying dataset and have a genuine hierarchical relationship.