Excel One Slicer for Multiple Pivot Tables: How to Connect

Charts & pivot tables · Updated November 21, 2026

Yes. In Excel for Microsoft 365 on Windows, one slicer can filter multiple PivotTables when they share a compatible data source—normally the same PivotCache, or the same workbook Data Model. Select the slicer, choose Slicer > Report Connections, and check the PivotTables you want it to control.

Why use one slicer for several PivotTables?

A slicer is a visible, clickable filter for a PivotTable. Instead of opening each PivotTable’s filter menu and selecting the same category repeatedly, you can click an item such as a region, product, or year once and have every connected PivotTable update together. This makes a report easier to use and helps keep related views aligned.

For example, a sales dashboard might show revenue by month, units sold by product, and sales by salesperson. If all three PivotTables use the same source data, a single Region slicer can filter each view to North, South, East, or West. Readers can compare the different measures for the same selection without having to apply the filter three times.

A slicer does not combine the PivotTables or make them share a layout. Each one remains a separate summary; the shared slicer simply sends the same field selection to each connected PivotTable.

How slicer connections work

Each PivotTable is built from a data source through a PivotCache, which stores and organizes data used by the table. Excel can connect a slicer to PivotTables that are compatible with that slicer’s source. In ordinary workbooks, the reliable requirement is that the PivotTables share the same PivotCache. PivotTables built from the workbook Data Model can also share slicers when they use that model.

Having columns with identical names or values is not enough. Two tables that both contain Region and Sales may still be based on separate caches, separate source ranges, or different models. Excel will then treat them as separate PivotTable groups, and the slicer’s connection list may not include both.

The PivotTables do not have to display the same fields in the same places. One might show sales by month and another by product. They can still respond to a slicer for a field in their shared source, provided that field is available to the PivotTables. The key issue is compatible source structure, not matching report layout.

Connect an existing slicer to multiple PivotTables

Use the following steps in Excel for Microsoft 365 on Windows:

  1. Click a cell in a PivotTable that already has a slicer, or create a slicer by selecting the PivotTable and choosing PivotTable Analyze > Insert Slicer. Select the field to filter, then choose OK.
  2. Click the slicer itself so that its contextual ribbon tab appears.
  3. Choose Slicer > Report Connections. In some Excel interfaces or documentation, this command is called PivotTable Connections.
  4. In the list, check each compatible PivotTable that the slicer should control, then choose OK.
  5. Click an item in the slicer and confirm that each connected PivotTable changes. Choose another item or clear the slicer selection to check the other states.

If the command is unavailable or a PivotTable is missing from the list, it is usually a source or cache compatibility issue rather than a problem with the slicer’s position or formatting. The following sections explain how to check and fix that.

Make PivotTables compatible

The simplest way to ensure that two ordinary PivotTables share a cache is to copy an existing PivotTable and then change the copy’s field layout. For example, copy the sales-by-month PivotTable, place the copy elsewhere, and rearrange its fields to show sales by product. A copied PivotTable retains the original cache, so Excel can generally offer both tables in the slicer’s Report Connections list.

For a new report, decide on the source before creating the PivotTables. Use the same Excel table or source range for the PivotTables you want to control together. Converting a structured range to an Excel table with Insert > Table can make the source easier to maintain as rows are added. Create the first PivotTable from that source, then copy it for additional views when practical.

If the report uses the Data Model, make sure the PivotTables are built from that model rather than creating some from the model and others from unrelated worksheet ranges. This is especially useful when a report combines related tables, such as Orders and Products, because the model can provide a shared basis for the PivotTables.

Do not assume that two PivotTables share a cache just because they were created from the same-looking data. Check the Report Connections list. If Excel does not offer one table as a connection, rebuild or copy the PivotTable from a compatible table, or reconsider how the report’s sources are organized.

Example: one Region slicer for three views

Suppose an Excel table named SalesData has columns for Date, Region, Product, Salesperson, Units, and Revenue. You create three PivotTables from that same source: monthly revenue, units by product, and revenue by salesperson. Add a Region slicer to one of the PivotTables and use Report Connections to select the other two.

When a user clicks West, each summary shows records for the West region. Selecting a different region changes all three summaries together. If the user selects more than one region, the PivotTables summarize the combined selection. The measure and grouping in each PivotTable remain distinct: the slicer filters records, while each PivotTable determines how the remaining records are summarized.

This distinction matters when interpreting a dashboard. A slicer selection is not a separate calculation applied to the visible numbers; it filters the underlying PivotTable data. If a PivotTable has additional filters of its own, those filters can also affect its result. For instance, one table could have a salesperson filter set to a single person while the other two show all salespeople.

Common connection problems and fixes

  • A PivotTable is missing from Report Connections: The tables may use different PivotCaches or sources. Copy a compatible PivotTable and adjust its layout, or rebuild the tables from a common source. For model-based reports, verify that the PivotTables use the same Data Model.
  • The slicer changes one table but not another: Reopen Report Connections and confirm that the second table is checked. Also check for other filters on that PivotTable, which may narrow its results further.
  • A new category does not appear in the slicer: Refresh the PivotTables after adding source rows. Use Data > Refresh All to refresh workbook connections and PivotTables, then check the slicer again. Confirm that the new rows are included in the source range; an Excel table usually expands more conveniently than a fixed range.
  • The slicer shows items with no visible results: The PivotTable may be retaining items from earlier source data, or another filter may make a selection empty. Refresh the PivotTable and review its field filters. Slicer settings can also affect whether items without data are displayed.
  • The connection command is not visible: Click the slicer, not a PivotTable cell, to show its contextual ribbon tab. If the command still does not appear, check the Excel version and whether the slicer is connected to a compatible PivotTable.

Refreshing does not repair unrelated PivotCaches by itself. If two PivotTables are built on separate caches, refreshing both updates their source data but does not necessarily make them connectable through one slicer.

Design and filtering details to plan for

A shared slicer is most useful when its meaning is clear across every connected view. A Region slicer is easy to interpret if all summaries represent regional sales. A slicer for a field that applies to only one view may confuse readers, even if Excel technically allows the connection. Label the slicer and arrange it near the summaries it controls.

One slicer can be connected to several PivotTables, and a PivotTable can have multiple slicers. For example, a dashboard can use shared Region and Year slicers. Each selection combines with the others, so choosing West and 2025 limits the connected PivotTables to records meeting both conditions. Consider the dashboard space required before adding many slicers.

Slicers are interactive controls, not just decorative labels. Users can select one or several items, depending on the slicer’s multi-select control, and can clear a filter with the clear-filter button on the slicer. Protecting a worksheet or workbook structure can affect how users interact with controls, so check the workbook’s protection settings if a slicer cannot be used.

In Excel for Mac, slicers are available, but ribbon labels and feature availability can differ by Excel version. Look for the slicer’s contextual tab and its connection command; if the connection option is missing, verify the version and confirm the PivotTables use the same compatible source. Excel for the web can display and interact with many workbook features, but desktop Excel is the safer place to create or troubleshoot PivotTable connections when the necessary command is not available in the browser.

When one slicer is not the right solution

If the PivotTables must remain based on separate sources, a single slicer may not be able to control them directly. The best fix is often to bring the data into a common source or Data Model and build compatible PivotTables from it. That approach takes some setup but avoids manually keeping several independent filters synchronized.

For a small report, separate slicers may be clearer than redesigning the data. Place one slicer beside each PivotTable and label each one so readers understand that the selections are independent. Another option is to use ordinary PivotTable report filters, though they are less visible and usually require users to open a dropdown for each table.

Choose based on the report’s purpose: use a shared slicer when readers should compare multiple summaries under the same selection; use separate controls when the views intentionally need independent filters; and consolidate the source when several reports need consistent filtering over time.

Frequently Asked Questions

Can one slicer control PivotTables on different worksheets?
Yes. The PivotTables can be on different worksheets as long as they are compatible with the slicer, typically because they share a PivotCache or use the same Data Model. Worksheet location alone does not prevent a connection.

Do the PivotTables need to have identical layouts?
No. They can summarize different fields in different ways. They need a compatible underlying source, and the slicer field must be available to the PivotTables it controls.

Why can’t I see one of my PivotTables in Report Connections?
It probably uses a different PivotCache or data source. Copying a compatible PivotTable and changing the copy’s layout is a practical way to create another view that can share the slicer.

Can I connect one slicer to a PivotChart as well?
A slicer can filter a PivotChart through its associated PivotTable. If the chart’s PivotTable is compatible, connect that PivotTable through Report Connections; the chart then reflects the filtered PivotTable.

Will the slicer include new items added to my source data?
Refresh the relevant PivotTables after adding data, and make sure the new rows are within the source. A structured Excel table can expand as rows are added, while a fixed range may need to be extended.

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.