Excel Slicers for Multiple Pivot Tables: How to Connect

Charts & pivot tables · Updated November 21, 2026

Yes. In Excel for Microsoft 365 on Windows, select the slicer, choose Slicer > Report Connections (called PivotTable Connections in some versions), then check the PivotTables it should control. The tables must use a compatible PivotTable cache or the same Data Model; if a table is missing from the list, it usually cannot share that slicer in its current setup.

What a slicer connection does

A slicer is a clickable set of buttons that filters a PivotTable by a field such as Region, Product, or Year. Connecting one slicer to several PivotTables makes a selection in that slicer filter each connected table at once. For example, clicking West can update a sales summary and a units-sold summary together, making it easier to compare different views of the same data.

The slicer does not combine the PivotTables, change their layouts, or delete rows from the source. It sends a filter selection to each connected PivotTable. Each table still calculates and displays its own measures, rows, columns, and totals. This is useful for dashboards because one visible control can keep multiple reports focused on the same category.

A connection is not automatic merely because two PivotTables show similar information or use columns with the same names. Excel needs the PivotTables to be compatible behind the scenes. That is why checking the connection list is an important part of building a report, not just a final formatting step.

Why PivotTable compatibility matters

Traditional PivotTables are built on a PivotTable cache, which stores and organizes the source data used by a report. A slicer can control multiple PivotTables when Excel considers them compatible, typically because they share the same cache. PivotTables made from different source ranges, separate caches, or incompatible data sources may not appear together as connection choices.

Creating two PivotTables from the same worksheet table does not guarantee that Excel will make them share a cache. Depending on how they were created, two reports that look as if they use the same data can still have separate caches. A practical way to keep reports compatible is to create the first PivotTable, then copy and paste it to make another PivotTable before changing its layout. The copied report generally retains the original cache.

For more complex workbooks, the Excel Data Model can be a better foundation. PivotTables created from the same Data Model can use fields from related tables, provided the model has suitable relationships. This approach is useful when a report combines, for example, sales transactions with separate product and date tables. A slicer field must still make sense for the PivotTables it is meant to filter.

Connect one slicer to multiple PivotTables

  1. Confirm that the PivotTables you want to control are compatible. If you are starting fresh, create the first report and copy it to make the additional reports, or build them from the same Data Model.
  2. Click one of the PivotTables. On the ribbon, choose PivotTable Analyze > Insert Slicer, select a field such as Region, and choose OK.
  3. Click the slicer so its contextual ribbon tab appears. Choose Slicer > Report Connections. In some Excel versions, the command is labeled PivotTable Connections.
  4. In the dialog, select each PivotTable that the slicer should control, then choose OK. If a PivotTable is not listed, see the troubleshooting guidance below; the dialog only offers eligible tables.
  5. Click a slicer button and verify that every intended PivotTable responds. Use the slicer’s clear-filter button to remove the selection and restore the unfiltered view.

To connect an existing slicer, skip the insert step and open its Report Connections dialog. To create another slicer, select a compatible PivotTable and insert one for another field. A Region slicer and a Year slicer can both control the same set of PivotTables, letting a reader narrow the report by two dimensions.

Example: one dashboard, two sales views

Suppose a workbook has an Excel table with Order Date, Region, Product, Units, and Sales columns. One PivotTable summarizes Sales by Product; another summarizes Units by Product. A Region slicer connected to both tables lets a manager choose East and see both revenue and unit volume for that region. The reports remain separate: one shows money, the other quantities, but both respond to the same selection.

If the dashboard also needs to show a year selection, add a Year field to the source data or use an appropriate date field, then insert a second slicer or a timeline where supported. Connect that control to the same eligible PivotTables. Selecting a region and a year applies both filters together. If a particular combination has no matching records, the PivotTable may show no detail or zeros depending on its layout and settings; that is not evidence that the slicer connection failed.

Before sharing a dashboard, test more than one selection. Choose an individual region, select multiple buttons if multi-select is enabled, and clear the filter. Check that totals and labels update as expected in every report. Clear labels such as Region and Year, consistent number formats, and aligned PivotTables help readers understand that the controls are shared.

When a PivotTable is missing from Report Connections

The most common cause is a cache or source mismatch. If a PivotTable is absent from the connection dialog, Excel is not offering it as a compatible target for that slicer. Compare how the tables were created and whether they use the same source or Data Model. Similar-looking fields do not by themselves establish a shared connection.

  • Build from a shared starting point: Copy a PivotTable that already uses the intended source, then change the copied table’s rows, columns, and values. This is often the simplest fix for ordinary PivotTables.
  • Use the same Excel table as the source: Convert a well-formed source range to an Excel table before creating reports. This makes the source easier to expand and select consistently, although using the same table alone does not guarantee that separately created PivotTables share a cache.
  • Use the Data Model for related tables: Add the required source tables to the workbook’s Data Model, define the relationships, and create the PivotTables from that model. This is a more involved setup but suits reports built from multiple related tables.
  • Rebuild a report if necessary: If an existing PivotTable has a different cache, it may be quicker to recreate it from a compatible PivotTable or model than to try to force a connection that Excel does not offer.

Check the field as well as the table. A slicer for Region can only filter reports meaningfully when the relevant Region field is available to those reports. With a Data Model, relationships and the direction in which filters can flow also matter. A missing or incorrect relationship can make a model-based report behave differently from what its field names suggest.

Other behaviors and practical limits

Connecting a slicer does not make every worksheet object respond. Ordinary cell ranges and formulas are not filtered just because a PivotTable slicer changes. PivotCharts that are based on a connected PivotTable generally follow that PivotTable’s filtering, but a chart built from unrelated cells is not automatically linked to the slicer. For a dashboard, verify the source of each chart and test it with the slicer.

Several slicers can affect the same PivotTable, and their selections work together as filters. For example, selecting West in Region and Furniture in Product narrows the report to records satisfying both selections. If a report appears blank, clear one or more slicers to see whether the combination simply has no matching data.

A slicer may show buttons for items that are not currently visible in a PivotTable, depending on the field and PivotTable settings. Likewise, refreshing the source can add or remove available items. If an item seems stale after a refresh, review the PivotTable and slicer settings rather than assuming the connection is broken. Slicers are report controls, not a substitute for checking source-data quality.

Windows, Mac, and web considerations

The instructions above use the Microsoft 365 desktop ribbon on Windows. In Excel for Mac, slicers and PivotTables are available in supported versions, but ribbon labels and the location of connection commands can vary by release. Select the slicer and look for its contextual Slicer tab and connection command; if the command or expected PivotTable is unavailable, confirm the Excel version and whether the tables share a compatible source setup.

Excel for the web has different feature coverage and interface details from the Windows desktop application. A workbook may contain PivotTables and slicers created in desktop Excel, but not every creation or management command is necessarily available in the same way online. For building or troubleshooting multi-PivotTable connections, use the desktop app when the web interface does not expose the required connection controls.

Frequently Asked Questions

Can one slicer control PivotTables on different worksheets?
Yes. Worksheet location is not the deciding factor. The PivotTables must be eligible in the slicer’s Report Connections dialog, which generally means they share a compatible cache or Data Model setup.

Why is my second PivotTable not listed in Slicer Connections?
It likely uses a different PivotTable cache or an incompatible source. Create the reports from a shared starting PivotTable, or use the same Data Model where appropriate. Matching field names alone do not make separate PivotTables connectable.

Can I connect a slicer to PivotTables with different layouts?
Yes, if the PivotTables are compatible and the slicer field is available to them. One table can summarize sales by product while another summarizes units by month; they do not need identical layouts.

Can one slicer filter a PivotChart and a PivotTable?
A PivotChart tied to a connected PivotTable usually reflects that PivotTable’s filter. A regular chart or an unrelated PivotTable will not necessarily respond. Check the underlying PivotTable and the slicer’s connection list.

Can I connect a slicer to a normal Excel table?
A PivotTable slicer is designed to filter its connected PivotTables, not arbitrary worksheet ranges. Excel tables have their own table-filter controls and table slicers, but those are a separate feature and do not automatically serve as connections for PivotTables.

Choosing the simplest reliable setup

For a straightforward dashboard based on one flat source table, create one PivotTable and copy it to make the additional reports, then insert and connect the slicer. This keeps the workflow simple and makes it easier to diagnose connection issues. For reports drawing on several related tables, the Data Model is often the more suitable structure, provided relationships are set up correctly.

In either case, make the intended filtering behavior part of the design: decide which reports should respond, connect only those, and test the dashboard with realistic combinations of selections. When a PivotTable does not appear in the connection dialog, treat that as a compatibility clue rather than a missing checkbox. Fixing the shared source or model setup is usually the key to making one slicer work across multiple PivotTables.

Related

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.