Excel Slicers Across Multiple Tables: How to Connect

How-to basics · Updated November 21, 2026

Yes—but it depends on what you mean by “tables.” A slicer can control multiple PivotTables when they share a compatible PivotTable source or Data Model; a slicer added to an ordinary Excel Table filters that table only and cannot directly control separate tables.

What “multiple tables” can mean in Excel

Excel uses “table” to describe two different things in this context. An Excel Table is a structured range created with Insert > Table. It has filter buttons in its header and can use slicers to filter its own rows. A PivotTable is a report built from data, and its slicers filter the report. People often call several PivotTables “tables,” even though those reports are not Excel Tables.

This distinction determines what a slicer can do. A slicer created for an Excel Table is connected to that one Table object. It does not have a Report Connections setting that lets it filter other, separate Excel Tables. A PivotTable slicer, by contrast, can be connected to more than one PivotTable when Excel considers their underlying sources compatible.

So the useful short version is: one slicer can control several PivotTables, but not several independent Excel Tables directly. To filter reports built from separate source tables, you may need to use the Data Model and relationships, or combine the source data into one table.

How slicer connections work

A slicer is a visual filter for a field, such as Region, Month, or Product. Clicking an item filters the connected report to records matching that choice. Multiple selections are possible, and the slicer can be cleared to show all items again. Slicers do not rewrite or delete source data; they change what the connected table or report displays.

For PivotTables, Excel keeps track of the PivotTable source and its cache or model. The cache is the stored structure and data used by a PivotTable report. When two PivotTables use a compatible shared cache, a slicer created for one can often be connected to the other. Excel then applies the slicer selection to both reports.

When the PivotTables use the Excel Data Model, a slicer can also filter multiple reports built from that model, provided the relevant field is available to those reports and the model relationships support the intended filtering. Merely using similarly named columns or tables is not enough. Excel needs an actual compatible connection between the reports and the field.

Connections are not the same as visual placement. You can move or resize a slicer without changing which PivotTables it controls. Conversely, placing a slicer beside several reports does not make it filter all of them; you must explicitly connect it to each report.

Connect one slicer to multiple PivotTables

In Excel for Microsoft 365 on Windows, first create the PivotTables and a slicer for a field that exists in the reports. Then use the slicer’s connection dialog:

  1. Click the slicer. The Slicer tab appears on the ribbon.
  2. Choose Slicer > Report Connections. Depending on the Excel build or context, the command may be called PivotTable Connections.
  3. In the dialog, select the check box for each PivotTable the slicer should control.
  4. Choose OK, then click an item in the slicer to confirm that each selected report responds.

If a PivotTable is missing from the list, Excel cannot connect that slicer to it in its current setup. The most common reason is that the PivotTables use different PivotTable caches or different data models. You cannot force an incompatible report into the connection list simply by changing its name or moving it onto the same worksheet.

For a PivotTable slicer, use PivotTable Analyze > Insert Slicer to add the slicer in the first place. Choose a field that makes sense across the reports, such as Region. Each connected PivotTable needs to support that field; a slicer for a field absent from a report cannot meaningfully filter that report.

On Mac, Excel provides slicers for PivotTables, but ribbon labels and available connection options can vary by version. Look for the slicer’s connection command after selecting it. Excel for the web may not offer every desktop command for creating or managing slicer connections, so use the Windows or Mac desktop app if the connection dialog is unavailable.

Why a slicer may not connect to another report

Two PivotTables can look alike and still be incompatible. For example, one may have been created from a worksheet range and another from a separate copy of that range. Even when both sources contain the same columns, Excel may have created separate caches. A slicer’s Report Connections list is the practical test: if the other report does not appear, it is not currently available to connect.

Other common causes include:

  • Different source types: One PivotTable might use a worksheet range while another uses the Data Model or an external connection.
  • Different fields: The slicer field may not exist in the other PivotTable’s source, or may have a different name or structure.
  • A normal Excel Table: A slicer made with Table Design > Insert Slicer is not a PivotTable slicer and cannot be added to PivotTable Report Connections.
  • Refresh or model issues: A report may need its source or model relationship checked before it can behave as expected.

To investigate, select each PivotTable and inspect its source using PivotTable Analyze > Change Data Source where that command is available. Check whether the reports use the same range or table and whether they were created in a compatible way. For Data Model reports, review the model’s tables and relationships. If the structures differ, rebuilding the reports from one consistent source is usually more dependable than trying to patch the connection afterward.

Using the Data Model for separate source tables

Suppose a workbook has an Orders table with Order Date, Product ID, and Amount, plus a Products table with Product ID, Category, and Product Name. A slicer for Category cannot filter an ordinary Orders Table by itself, because Category is stored in the separate Products table. But you can load both tables into the Data Model, create a relationship using Product ID, and build PivotTables from that model. A Category slicer can then filter model-based reports when the relationship and report fields allow it.

The relationship matters: the Product ID values must connect the records correctly, and the model must have a valid relationship between the tables. A slicer filters through that relationship; it does not merge the source sheets or add Category as a physical column to every row in Orders. A poorly designed or missing relationship can leave a slicer with no effect on a report, or make the results misleading.

For a new PivotTable, use Insert > PivotTable and choose the option to add the data to the Data Model when appropriate. The exact dialog wording can depend on how the source was selected. Create the required relationships in the Data Model, then build the reports from the model. This approach is useful when tables represent related entities, such as customers, transactions, and products; it is more complex than a single flat table and requires careful relationship design.

A practical example: sales reports by region

Imagine a workbook with three PivotTables: sales by month, sales by salesperson, and order count by product. If all three are based on the same sales source and can share a PivotTable cache, add a Region slicer to one report and use Report Connections to select the other two. Clicking “West” then filters all three reports to that region. The reports can show different measures and layouts while responding to the same selection.

If the sales-by-product report instead uses a separate copy of the source range, it may not appear in the connection dialog. Recreate that report from the same source in a compatible way, or build the reports from a shared Data Model. If the source information lives in related tables, use model relationships rather than expecting a slicer on one ordinary Table to reach into another.

You can connect more than one slicer to the same PivotTable as well. For example, Region and Year slicers can both affect the reports. Their filters combine: choosing West and 2025 displays records that satisfy both selections. A clear-filter button on a slicer removes that slicer’s selection; it does not necessarily clear other slicers or every filter applied elsewhere.

Choosing the right approach

The best setup depends on whether the goal is to filter raw rows or coordinate analytical reports. A single Excel Table with a slicer is straightforward for browsing a list. Multiple PivotTables with shared connections suit a dashboard where several summaries need to respond together. Related source tables are a strong reason to consider the Data Model. If the source tables are unrelated, forcing them under one slicer may not have a clear or meaningful filtering result.

  • One source list, one filtered view: Format the range as an Excel Table and add a slicer with Table Design > Insert Slicer.
  • Several summary reports from the same source: Build compatible PivotTables, add a PivotTable slicer, and select the reports in Report Connections.
  • Several related source tables: Use the Data Model and create appropriate relationships before building the reports.
  • Several independent lists that must filter together: Consider combining them into a consistent source table if their columns and meaning align. Otherwise, use separate slicers or redesign the report around a clearly defined shared field.

Combining data is not always the right answer. For example, stacking monthly sales records with the same columns can create one useful fact table. Combining a list of employees with a list of office locations by simply appending rows would not create a meaningful shared dataset. Choose a structure based on what each row represents and how the records relate.

Common misconceptions and useful checks

A slicer is not a universal workbook filter. It only affects the Table or PivotTables to which it is connected. It also does not automatically filter formulas, charts built from unrelated ranges, or another worksheet’s data. A chart linked to a connected PivotTable will generally reflect the filtered PivotTable, but a standard chart based on a separate range will not become connected just because it sits nearby.

Before publishing a dashboard, test more than one slicer choice and confirm that each intended report changes. Check that “no data” results are understandable, that the slicer’s clear-filter control is visible, and that users can distinguish which reports it controls. If a report should remain unaffected, leave it unchecked in Report Connections. Naming PivotTables clearly can also make the connection dialog easier to use, especially in a workbook with many reports.

Frequently Asked Questions

Can one slicer control two Excel Tables?
No. A slicer inserted for an ordinary Excel Table filters that Table only. To coordinate multiple reports, use compatible PivotTables or build reports from a Data Model.

Can one slicer control multiple PivotTables?
Yes, when Excel can connect the PivotTables through a compatible shared cache or Data Model. Select the slicer, open Report Connections or PivotTable Connections, and check the reports to control.

Why is my second PivotTable missing from Report Connections?
It likely uses an incompatible source or PivotTable cache, or it lacks the slicer field. Check its source and model, then rebuild the reports from a common compatible source if needed.

Can a slicer filter tables on different worksheets?
Worksheet location is not the deciding factor. A PivotTable slicer can control compatible PivotTables on different sheets when they are selected in Report Connections. An ordinary Table slicer still filters only its own Table.

Will a slicer filter a chart too?
A PivotChart associated with a connected PivotTable follows that PivotTable’s filtering. A standard chart based on a separate range does not automatically respond to the slicer.

Related

Try it: the Date Difference Calculator: days, months, years and weekdays between two dates, with the DATEDIF formulas.

More in How-to basics

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.