Yes, an Excel slicer can control multiple PivotTables when they share a compatible PivotTable cache or use the same Data Model. A slicer created for a regular Excel table, however, filters only that table; to filter separate tables together, use compatible PivotTables or combine the data first.
What “multiple tables” can mean in Excel
The answer depends on whether “table” means an Excel Table or a PivotTable. An Excel Table is a structured range of data, usually created with Insert > Table. It has filter arrows in its header and can have a slicer for selected columns. A PivotTable is a summary report built from source data, and its slicers have a separate connection feature that can link compatible PivotTables.
That distinction explains why adding a slicer to one ordinary table does not automatically make it filter another ordinary table on the same worksheet. The two ranges are separate filter objects, even if they contain similar columns or are side by side. In contrast, PivotTables can share a slicer when Excel recognizes that they use a common underlying cache or Data Model.
- Several Excel Tables: A table slicer filters its associated table, not other independent tables.
- Several PivotTables: A PivotTable slicer can filter more than one compatible PivotTable through Report Connections.
- Mixed or separate sources: A shared Data Model, relationships, or a combined source may be needed.
How a slicer filters PivotTables
A slicer is a visual filter. Its buttons represent values from a field, such as Region, Product, or Year. Clicking a button tells a connected PivotTable to show records matching the selected value; selecting more than one button applies a multi-value filter. The slicer does not merge tables or change the source records. It changes what the connected PivotTables display.
For several PivotTables to respond together, Excel needs a compatible filtering structure behind them. The simplest case is PivotTables created from the same source and sharing the same PivotTable cache. A cache is Excel’s stored representation of the source data used by a PivotTable. Two PivotTables can look alike and use the same worksheet range but still have different caches, so visual similarity alone does not prove they can share a slicer.
When a slicer is selected, the Report Connections control lists PivotTables it can control. If a PivotTable is absent or unavailable in that list, Excel does not consider it compatible with that slicer. The remedy is usually to rebuild or copy the PivotTables using a common source/cache, or to create them from a properly related Data Model.
Connect a slicer to multiple PivotTables
In Excel for Microsoft 365 on Windows, first create the PivotTables and confirm that they can be connected. Insert the slicer from one of them, then select which compatible reports it should filter.
- Click inside a PivotTable and choose PivotTable Analyze > Insert Slicer.
- Select the field to use as a filter, such as Region, and choose OK.
- Click the slicer. Open the Slicer tab, then choose Report Connections. Depending on the ribbon layout, the command may be labeled PivotTable Connections.
- Check the PivotTables that should respond and choose OK. Test the slicer by selecting a value and confirming that each intended report changes.
If your second PivotTable is not listed, do not assume there is a hidden checkbox that will force the connection. Check its source and cache. A reliable approach when reports summarize the same data is to copy the original PivotTable, paste the copy, and then change its fields and layout. The copy shares the original cache; creating a new PivotTable independently can result in a separate cache.
On Excel for Mac, slicers and PivotTables are available, but ribbon labels and the availability of connection commands can vary by version. Look for the selected slicer’s connection options and confirm that the other PivotTable appears. Excel for the web also has more limited PivotTable authoring features than the Windows desktop app, so use the desktop app if you cannot create or manage the needed connections there.
When separate source tables need a Data Model
If the reports draw on different source tables, a Data Model can provide a shared foundation. The Data Model is Excel’s built-in relational layer: it can hold multiple tables and use relationships to connect them by common fields. For example, a Sales table might contain OrderDate, ProductID, and Amount, while a Returns table contains ReturnDate, ProductID, and Quantity. A Products table can relate to both through ProductID.
For a slicer to filter PivotTables built from different fact tables, the model must have relationships that let the selected field reach each report’s data. A Product slicer based on the Products table can filter both Sales and Returns when that table is correctly related to both. A slicer based on a column in the Sales table alone may not filter the Returns PivotTable as intended. Prefer a shared lookup or dimension table for fields that need to filter multiple reports.
To start building a model, add each source table to the Data Model when creating a PivotTable, or use Power Pivot features where available. Then create relationships between matching key columns and build the reports from the model. Relationship keys should have compatible data types, and the lookup side should contain unique values. For instance, a Products table should ordinarily have one row per ProductID; duplicated lookup keys can prevent a clean one-to-many relationship.
Relationships are not the same as matching column names. Excel does not automatically know that two columns called Region refer to the same set of categories, nor can a relationship reliably connect records when the key values are inconsistent. Clean values, stable identifiers, and a deliberate model design matter more than the slicer formatting.
Choose between combining data and relating tables
For many workbooks, putting records into one well-structured source table is simpler than maintaining a model. If monthly sheets contain the same columns, append their rows into one table and add a Month or Source column. Then build multiple PivotTables from that combined table and connect them to a slicer. This works well when each row describes the same kind of record and the columns have consistent meanings.
Power Query is useful for repeatable combination. In Excel for Windows, use Data > Get Data to import or connect to sources, then use the Power Query Editor to append queries with matching columns. Load the resulting query to a worksheet table or to the Data Model, depending on the design. When the source files change, refresh the query rather than copying and pasting the new rows by hand. Append adds rows; merge joins columns based on matching keys, so choose the operation that matches the data.
Keep separate related tables when they represent different kinds of information, such as transactions, products, and customers, or when a flat combined table would duplicate a large amount of descriptive data. A model is also useful when the same lookup fields should filter multiple fact tables. Conversely, if separate lists are unrelated and have no meaningful common field, one slicer cannot sensibly apply a selection across them just because they appear on the same sheet.
Designing a useful shared-slicer report
A shared slicer is most helpful when users need to compare summaries under the same selection. For example, a dashboard might show sales by month in one PivotTable and returns by product in another. Connecting both to a Product Category slicer lets a reader compare the reports for the same category without changing each report’s filter separately.
Before distributing the workbook, check the following:
- Use a field whose values have the same meaning across all connected reports.
- Give PivotTables and slicers clear names so Report Connections is easier to manage.
- Test single selections, multiple selections, and clearing the filter; the clear-filter icon is on the slicer.
- Make sure each report has the same expected response. A blank report can be a valid result when the selected value has no matching records.
- Refresh the source data and test again. New categories may appear after refresh, and model relationships or source ranges may need attention.
One slicer can filter multiple PivotTables, but it does not require every PivotTable on a sheet to respond. Select only the reports that are meant to share the selection. This is particularly important on dashboards: connecting unrelated reports can make a slicer appear broken or produce empty outputs that confuse readers.
Common problems and practical fixes
The other PivotTable is missing from Report Connections. It may use a separate cache, a different source, or a different Data Model. Recreate it from the same model or copy a compatible PivotTable and adjust its layout. Verify that the second report is actually a PivotTable, not a normal range or Excel Table.
The slicer filters one report but not another. Reopen Report Connections and confirm the second report is checked. If it is checked but the selection has no visible effect, confirm the slicer field is connected to the second report’s source and that matching values exist. In a Data Model, inspect whether the relationships provide a valid path from the slicer’s table to the second report’s table.
The source table grew, but new rows are not included. Check that the source is an Excel Table or that the PivotTable’s source range includes the added rows, then refresh. A table generally expands as rows are added directly beneath it, but pasted data or a manually specified range can lead to missed records. For Power Query sources, refresh the query and then refresh the PivotTable if necessary.
A regular table slicer will not connect to a PivotTable. These slicers are not interchangeable. A slicer added through Table Design > Insert Slicer filters its Excel Table. A PivotTable slicer is created from PivotTable Analyze > Insert Slicer and uses Report Connections. If both kinds of output must respond to the same choice, consider building the outputs as PivotTables from one shared source, or use a designed model/reporting approach rather than expecting one slicer to control unrelated objects.
Frequently Asked Questions
Can one Excel slicer control two PivotTables?
Yes. Select the slicer and use Slicer > Report Connections to select both PivotTables. They must share a compatible cache or be based on a model that supports the same filter field.
Can one slicer filter two ordinary Excel Tables?
No, not directly. A slicer created for a regular Excel Table filters that table only. To coordinate filtering across separate sources, combine the records, use compatible PivotTables, or build a Data Model with appropriate relationships.
Why is my PivotTable missing from Report Connections?
Most often, it was created with a different cache, source, or Data Model. Rebuild it from the same model or make a copy of the compatible PivotTable, then adjust the copied report’s fields and layout.
Can a slicer filter PivotTables from different worksheets?
Yes. Worksheet location does not prevent a connection. The PivotTables still need to be compatible, and they must appear as selectable reports in the slicer’s Report Connections list.
Do slicers work with Power Query data?
Yes, if the query output is loaded as a table and used as a PivotTable source, or loaded to the Data Model and used to create model-based PivotTables. A slicer for the resulting PivotTable follows the PivotTable connection rules; Power Query itself does not make unrelated tables share a slicer.
What is the simplest way to make several reports respond together?
When the reports use the same kind of records, combine those records into one clean source table, create the PivotTables from that source, and connect the slicer through Report Connections. Use a Data Model when the sources are genuinely related but should remain separate.
Related
- Password Protect an Excel Sheet as Read-Only
- Password Protect an Excel Sheet From Viewing: What Works
- Password Protect an Excel Sheet from Editing Safely
Try it: the Date Difference Calculator: days, months, years and weekdays between two dates, with the DATEDIF formulas.
More in How-to basics
- Google Sheets vs Microsoft Excel: Which Should You Use?Google Sheets and Microsoft Excel are spreadsheet programs for organizing data, calculating results, and making charts. Sheets is…
- How to Center Anything on a Page in Excel for PrintingTo center worksheet content on a printed page in Excel for Microsoft 365 on Windows, open Page Layout…
- Snowball Effect Debt Spreadsheet: Build and Use OneA snowball effect debt spreadsheet helps you list debts from smallest balance to largest, pay each minimum, and…
- Google Sheets: Count Checked and Unchecked CheckboxesTo count checked checkboxes in Google Sheets, use =COUNTIF(A2:A20,TRUE), assuming the checkboxes are in A2:A20 and use the…
- Google Sheets Expense Tracker: Setup and Tips That WorkA Google Sheets expense tracker is a spreadsheet for recording purchases and summarizing where your money goes. Create…
- Excel Headers: How to Add Them to Every Printed PageTo add a header that repeats on every printed page in Excel for Microsoft 365 on Windows, choose…
Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources
Spotted an error in this guide? Let us know.