Can Excel Slicers Connect to Multiple Tables Directly?

In Excel, a slicer added to a regular Table filters that Table; it does not directly control other independent Tables. To use one slicer across multiple reports, build the reports as PivotTables that share a PivotTable cache or the Excel Data Model, then use the slicer’s Report Connections. The right method depends on whether your tables are independent lists or related parts of one dataset.

What an Excel Table slicer controls

An Excel Table is a structured range with column headers, built-in filtering, and features such as automatic expansion when you add rows. Select a cell in the Table, choose Table Design > Insert Slicer, and select one or more columns. Excel creates buttons for the available values in those columns. Clicking a button filters the Table to matching records; choosing more than one value narrows the displayed rows to records matching the selected values.

That control belongs to the Table it was created for. For example, if you have separate Tables named Orders and Returns, a slicer for Orders[Region] does not automatically filter the Returns Table, even if both have a Region column and use the same labels. Matching column names, similar data, or placement on the same worksheet do not make two Tables connected.

This distinction matters because Excel uses “Table” for a structured range and “PivotTable” for a summarized report. Their slicers look similar, but their connection options are different. A Table slicer is useful for interactively narrowing one list. A PivotTable slicer can sometimes control several PivotTables, provided those reports share a compatible source connection.

How PivotTable slicer connections work

To create a slicer for a PivotTable, select a cell in the PivotTable and choose PivotTable Analyze > Insert Slicer. Select a field, such as Region, Product, or Month. To use the slicer with other PivotTables, select the slicer and choose Slicer > Report Connections. Depending on the Excel build and context, the command may be labeled PivotTable Connections.

The dialog lists PivotTables the slicer can control. Check the reports you want, then select OK. If a PivotTable is missing from the list, it usually does not share the slicer’s PivotTable cache or compatible Data Model connection. The fact that two reports use columns from the same worksheet is not enough. A PivotTable cache is the stored source and structure that a PivotTable uses, and Excel limits a slicer’s connections to compatible reports.

A practical way to make several reports share a cache is to create the first PivotTable and then copy and paste it to make the next report. You can change the copied PivotTable’s layout and fields while retaining its shared cache. When reports are created separately, even from the same Table, Excel may create separate caches; if so, the slicer may not offer both reports as connections.

Use the Data Model for related Tables

If the records genuinely belong in separate Tables, the Data Model is usually the more scalable way to analyze them together. For instance, an Orders Table might contain one row per transaction, while a Products Table contains one row per product with its category and description. Rather than copying product details into every order row, you can add both Tables to the workbook’s Data Model and relate them through a shared key, such as ProductID.

A relationship lets a PivotTable combine fields from related Tables. A slicer using a field from the Products Table, such as Category, can then filter measures based on Orders through that relationship. This is different from linking two worksheet filters: the model defines how records in one Table relate to records in another.

For a Windows workflow, make sure the source ranges are formatted as Excel Tables and have clear, unique column names. Add the Tables to the Data Model using the available Power Pivot commands, or include them in the model when creating a PivotTable if that option is available. Then choose Data > Relationships to create a relationship between matching columns. The column on the one side should contain unique values; the related column on the many side can repeat those values. For example, each ProductID should appear once in Products, but it can appear in many Orders rows.

Create a PivotTable from the Data Model and use fields from the related Tables. Insert a slicer from an appropriate field, then use Report Connections to select other PivotTables built from that same model. The model does not infer every relationship automatically: choose keys that represent the same kind of identifier, check for blanks or inconsistent values, and confirm that the relationship reflects the real structure of the data.

Steps for connecting one slicer to multiple reports

Choose the reporting structure. If you only need to filter one list, use a Table slicer. If you need one control for several summaries, plan to use PivotTables with a shared cache or the Data Model.
Prepare the source data. Give each range a header row, consistent data types, and a stable field for matching records. Convert ranges to Tables with Home > Format as Table if they are not already Tables.
Create the reports. Make PivotTables from a shared source or from the Data Model. For related Tables, establish and check their model relationships before relying on cross-table filtering.
Insert the slicer. Select a PivotTable, choose PivotTable Analyze > Insert Slicer, and choose the field that should act as the control.
Connect the reports. Select the slicer, open Slicer > Report Connections or PivotTable Connections, check the compatible PivotTables, and confirm.
Test the result. Click a few slicer buttons and verify that each intended report changes correctly. Clear the selection afterward so readers do not mistake a filtered view for the full dataset.

These steps describe Excel for Microsoft 365 on Windows. Excel for the web can display and interact with many existing PivotTables and slicers, but advanced Data Model and Power Pivot authoring options are not equivalent to the Windows desktop workflow. Excel for Mac also differs: Power Pivot and some Data Model management capabilities are not available in the same way as on Windows. If the workbook depends on model relationships, create and maintain that model in desktop Excel for Windows, then verify the workbook’s behavior in the version where it will be used.

Choosing between a Table slicer and a PivotTable slicer

Use a Table slicer when the goal is to let someone scan and filter a single detailed list. A sales coordinator might filter an Orders Table to show only one salesperson’s records, then inspect individual transactions. It is straightforward and does not require building a summary report.

Use PivotTable slicers when the goal is to control one or more summaries. A manager might want a Region slicer to update a revenue PivotTable, an order-count PivotTable, and a product-category PivotTable together. Make those reports share a cache or use the same Data Model, and check the Report Connections dialog rather than assuming they are linked.

Use the Data Model when the source information is split across related Tables or when repeating descriptive data would make a single flattened Table cumbersome. It is particularly useful when you need fields from separate entities in one report. It does require more careful setup: identifiers must match, the relationship direction and uniqueness must be sound, and users need a compatible Excel environment to maintain the model.

Common connection problems

The second PivotTable is not listed. It may have a separate cache or use a different source connection. Recreate it by copying a compatible PivotTable, or rebuild the reports from the same Data Model where that suits the data.
The slicer changes one report but not another. Open Report Connections and check whether the other PivotTable is selected. Also confirm that the reports are compatible; selecting a checkbox cannot connect an unrelated Table or an incompatible PivotTable.
A Data Model relationship cannot be created. Check that the intended one-side key has unique values and that both relationship columns contain compatible data. Text values that look like numbers, extra spaces, missing keys, and duplicate IDs can prevent a useful relationship.
The slicer has unexpected items. Source data may include inconsistent spelling, blanks, or old values retained in a PivotTable cache. Clean the source and refresh the PivotTable. A slicer reflects the field’s available values, so inconsistent labels may appear as separate buttons.
The list or report seems stale. A slicer does not replace data refresh. Refresh the PivotTable after changing its source data, and confirm that new rows are included in the source Table or model. A worksheet Table slicer filters its current Table; it does not combine or refresh separate lists.

Alternatives when Tables must stay separate

If you cannot use PivotTables or the Data Model, there is no built-in setting that makes one ordinary Table slicer filter several independent Tables. Consider whether the reports can be redesigned around one consolidated Table, or whether related data can be modeled properly rather than kept as parallel lists.

For a small workbook, separate slicers may be the clearest choice: add one to each Table and explain that each control filters only its own list. For a formula-driven report, a shared dropdown or other input cell can drive formulas that return filtered views, but that is a separate design and requires formulas compatible with the Excel versions used by readers. It is not a Table slicer connection. For larger repeatable transformations, Power Query can combine or reshape source data before reporting; it prepares data but does not make independent worksheet Table slicers synchronize.

Avoid merging Tables merely because their columns have similar names. Combining them is sensible when rows describe the same kind of record and can share a consistent schema. If one Table describes products and another records orders, joining or relating them requires a key and a clear understanding of whether the relationship is one-to-many. Choosing the structure first prevents confusing reports and misleading totals.

Frequently Asked Questions

Can one slicer filter two Excel Tables?
A slicer inserted from a regular Excel Table filters that Table, not two independent Tables. To control multiple reports, use compatible PivotTables and connect them through Report Connections, or build the reports from a shared Data Model.

Why is Report Connections greyed out?
The slicer may belong to a regular Table rather than a PivotTable, or Excel may have no compatible PivotTables to list. Select a PivotTable slicer and check that the intended reports share its cache or Data Model connection.

Can a slicer connect PivotTables from different worksheets?
Yes. Worksheet location is not the deciding factor. The PivotTables must be compatible with the slicer, and you must select them in Report Connections.

Do two PivotTables from the same Table automatically share a slicer?
Not necessarily. Excel can create separate PivotTable caches when reports are created separately. Check Report Connections; copying an existing PivotTable or using a shared Data Model can help keep reports compatible.

Can a slicer filter a chart and a Table at the same time?
A PivotChart connected to a PivotTable responds to that PivotTable’s slicer. A regular worksheet Table is not added as a slicer connection merely because it appears beside the chart. Use a shared PivotTable-based design if both visual reports should respond together.

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.