Cross-Filtering

Cross-filtering lets widgets on a dashboard interact with each other. When a viewer selects data in one widget, other related widgets automatically filter to show only the matching data.

How it works

Cross-filtering creates relationships between queries used by different widgets. When a viewer clicks on a data point in one widget (e.g., a bar in a chart, a region on a map), the selected value is used to filter the data in other widgets that have a cross-filter relationship.

For example, on a retail dashboard:

1. A viewer clicks on "North Region" in a bar chart
2. A map widget filters to show only stores in the North Region
3. A table widget filters to show only transactions from the North Region
4. A metric widget updates to show revenue for the North Region only

Configuring cross-filter relationships

In the dashboard builder, you define cross-filter relationships by specifying:

• Source query - the query whose widget triggers the filter
• Target query - the query whose widget receives the filter
• Column mapping - which column in the source corresponds to which column in the target

For example, if your bar chart shows data from sales_summary and your table shows data from transaction_detail, you might map the region column in both queries so that selecting a region in the chart filters the table.

Cross-filtering with slicers

Slicers are designed specifically to trigger cross-filtering. When a viewer changes a slicer value (e.g., selecting a date range or choosing a category from a dropdown), the selection filters all widgets that have a cross-filter relationship with the slicer's query.

Tips

• Cross-filtering works best when your queries share common dimensions (like region, date, or category)
• You can create multiple cross-filter relationships on a single dashboard for rich interactivity
• Viewers can typically clear a cross-filter selection to return to the unfiltered view