Excel Slicer Link to Different Pivot Tables: How It Works

Yes. In Excel for Microsoft 365 on Windows, one slicer can filter multiple PivotTables when those PivotTables share a compatible PivotTable cache or workbook Data Model. Select the slicer, choose Slicer > Report Connections (sometimes labeled PivotTable Connections), and check the PivotTables it should control.

What it means to connect a slicer

A slicer is a clickable set of filter buttons for a PivotTable. For example, a slicer for Region can show buttons such as East, Central, and West. Clicking West filters the connected report or reports to that selection. A slicer is a visual control; it does not delete rows from the source data or change the underlying records.

Connecting one slicer to different PivotTables is useful when a worksheet has several views of the same data. A sales dashboard might show revenue by month, units by product, and sales by salesperson. If all three PivotTables can use the same Region field and share the relevant cache or Data Model, one Region slicer can keep the views aligned as a reader changes the selection.

The key qualification is that the PivotTables must be compatible. Having the same-looking field names, or even pointing to ranges that contain similar data, does not by itself guarantee that Excel will offer every PivotTable in the connection list. The underlying cache or model matters.

What PivotTables can share a slicer

For ordinary PivotTables, Excel uses a PivotTable cache to hold and work with source data. A slicer can be connected to PivotTables that share a compatible cache. A practical way to create such reports is to copy an existing PivotTable and then change the copy’s layout—for example, move Month from Rows to Columns or replace Product with Salesperson. This commonly keeps the reports on the same cache, making them candidates for one slicer.

PivotTables built separately can sometimes share a cache, but do not assume they do simply because they use the same worksheet range or table. Differences in how the reports were created, their source definitions, or their connections can leave them on separate caches. The Report Connections list is the decisive check: if a PivotTable is not listed, Excel cannot connect that slicer to it in the current setup.

PivotTables based on the workbook Data Model can also share a slicer when they use the same model and the field is available to the reports. The model can include related tables, so a slicer field from one table may filter measures based on another through the model’s relationships. A missing or incorrect relationship can prevent the expected filtering even though the tables are in the model.

Shared cache: Often the simplest arrangement for several reports built from one source table.
Shared Data Model: Useful when the report draws on multiple related tables or model measures.
Separate sources or connections: These may require a different design; a slicer cannot bridge unrelated PivotTable caches just by being copied.

Connect one slicer to multiple PivotTables

First create the PivotTables and confirm that each one has the field you want to use as the slicer—for example, Region. It is fine if the field is not currently displayed in the PivotTable layout; the important point is that the PivotTable’s source or model supports it. Then follow these steps in desktop Excel for Microsoft 365 on Windows:

Click inside a PivotTable and choose PivotTable Analyze > Insert Slicer.
Select the field to filter, such as Region, and choose OK. Excel places a slicer on the sheet.
Click the slicer so its contextual ribbon tab appears. Choose Slicer > Report Connections. Depending on the build or context, the command may be called PivotTable Connections.
In the dialog, check each compatible PivotTable that the slicer should control, then choose OK.
Click a slicer button and verify that every selected report changes. Choose the slicer’s clear-filter icon to remove the selection and return to the unfiltered view.

The names in the connections dialog can be generic or confusing, especially if several PivotTables have similar layouts. Give each PivotTable a distinct name before connecting them. Click inside a PivotTable, open PivotTable Analyze, and edit the PivotTable Name box at the left of the ribbon. Clear names such as SalesByMonth and UnitsByProduct make it easier to select the intended reports.

A practical dashboard example

Suppose an Excel table called SalesData contains OrderDate, Region, Product, Salesperson, Units, and Revenue. You create three PivotTables from this data: revenue by month, units by product, and revenue by salesperson. To make a Region slicer control all three, create the first PivotTable, copy it twice, and rearrange the copies to produce the other views. Insert a Region slicer from one report, open Report Connections, and select all three PivotTables.

Now selecting West filters the revenue-by-month, units-by-product, and salesperson reports to West, provided the reports share the cache and each recognizes the Region field. Selecting East afterward changes the reports together. This is different from adding three separate Region slicers: one control gives the dashboard a single, consistent selection, which reduces the chance that a reader compares reports filtered to different regions.

A slicer can also filter more than one field through multiple slicers. For example, put Region and Product slicers on the dashboard. Selecting a region and then a product applies both selections to the connected reports. If users need to select several slicer items at once, use the slicer’s multi-select control when available, or hold Ctrl while selecting items in Windows. The exact interaction can depend on the Excel build and slicer configuration.

Why a PivotTable may not appear in Report Connections

If the target report is missing from the dialog, check the data structure before rebuilding the dashboard. These are the common causes and practical checks:

The PivotTables use different caches. Create a new report by copying a PivotTable that already works with the slicer, then adjust its layout. If the reports must remain separate, consider rebuilding them from a common source or using the Data Model where appropriate.
The reports use different sources or connections. Confirm that the source table, range, or external connection is the one intended. Two sources with similar columns are not necessarily one shared cache.
The slicer field is unavailable in a report. Check that the field exists in that PivotTable’s source or model. In a Data Model report, also check that the tables have the relationships required for the filter to reach the measure.
The target is not a PivotTable. A slicer attached to an Excel table is not the same as a PivotTable slicer. Table slicers filter their own table; they do not automatically control PivotTables.
The PivotTable is on another worksheet or has a different name. That alone is not a reason it cannot connect, but it can make it harder to identify. Review the connection list carefully and rename reports clearly.

Changing a PivotTable’s data source is not always a quick fix, especially for reports using the Data Model or an external connection. Before changing sources, save a copy of the workbook and consider whether the reports should instead be rebuilt from one shared cache or model. A workbook can contain multiple source tables and still support a coordinated dashboard, but the model and relationships need to be designed for that purpose.

Filtering, refreshing, and keeping reports consistent

A slicer selection is a filter state, not a permanent change to the source data. Refreshing a PivotTable updates its report from the source, but it does not make incompatible caches compatible. If new records or new categories are added, refresh the PivotTables and check that the slicer displays the expected items. Depending on the source and refresh behavior, old items may remain in a slicer even when they no longer appear in the current data; review PivotTable options if that creates confusion.

When a slicer controls several reports, the reports should be interpreted as sharing the same selection. However, different layouts, calculations, filters, or source coverage can still make their totals differ. For instance, a report may have an additional Product filter or a value field summarized differently. A shared Region slicer does not remove those other differences; it applies its own selection alongside them.

For a polished dashboard, place the slicer near the reports it controls, use clear headings, and test several choices—including clearing the filter. If a workbook contains multiple slicers, check each slicer’s Report Connections separately. A PivotTable can be connected to one slicer but left out of another, so a dashboard may otherwise appear to respond inconsistently.

Excel for Mac and Excel for the web

The steps above use the Windows desktop ribbon. Excel for Mac has PivotTable and slicer features, but ribbon labels and available commands can differ by version and update. Select the slicer and look for its contextual Slicer tab and a Report Connections or PivotTable Connections command. If the connection command is unavailable, update Excel and check the current feature support for that build; Windows desktop Excel is a useful place to configure the workbook when the Mac interface does not expose the option.

Excel for the web can display and interact with many workbook features, but its editing controls are not identical to the full desktop application. If you cannot create or edit the required connections in the browser, open the workbook in desktop Excel, configure the slicer there, save it, and then check the workbook in the web app. Avoid assuming that every desktop ribbon command has a matching browser command.

Frequently Asked Questions

Can one slicer control two PivotTables?
Yes, if both PivotTables are available in the slicer’s Report Connections dialog. They generally need to share a compatible PivotTable cache or use the same Data Model.

Why can’t I see my other PivotTable in the slicer connections?
The reports may use different caches, sources, or model connections. Try copying a compatible PivotTable to create the second report, or review whether both reports should be rebuilt from a common source.

Can I connect a slicer to PivotTables on different sheets?
Yes. Worksheet location does not by itself prevent a connection. Select the slicer’s Report Connections command and check the compatible PivotTables, wherever they are in the workbook.

Can a slicer control a PivotTable and a regular Excel table?
Not through one shared slicer connection. A slicer for a table filters that table, while a PivotTable slicer connects to compatible PivotTables. To coordinate different objects, you may need separate controls or a redesigned report.

Will refreshing break the slicer connection?
A normal refresh does not inherently break a valid connection, but it does not fix different caches either. After changing sources or rebuilding reports, reopen Report Connections and confirm that the intended PivotTables remain checked.

Choosing the simplest setup

For a few reports based on one flat source table, use PivotTables that share a cache—copying an existing PivotTable is often the most direct way to keep them together—and connect a single slicer through Report Connections. For reports built from several related tables, use the workbook Data Model and make sure its relationships support the slicer field. If Excel does not list a report as a connection option, treat that as a structural limitation to resolve, rather than expecting a slicer to synchronize unrelated PivotTables automatically.

Try it: the Percentage Formula Generator: percent of, percent change, increase and decrease, with the formula.

More in Charts & pivot tables

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

Spotted an error in this guide? Let us know.