This is a problem that should not exist. The user has already done the hard work: an organized table, working filters, a total row, slicers in place. They need a summary that respects those filters. And Excel, for all its power, makes this surprisingly difficult. The SUBTOTAL function was a good try, but it only returns a single number, not a dynamic table. The user is not asking for something exotic. They are asking for a basic, logical workflow: filter here, see the filtered total over there. The fact that this requires workarounds is not a failure of the user. It is a limitation of the tool.
Here is the practical reality. Excel does not have a native function that says "give me a new table that mirrors this filtered view." The closest path involves using the AGGREGATE function or, more reliably, building a summary with formulas that check the SUBTOTAL visibility of each row. A common approach is to add a helper column that uses `=SUBTOTAL(103, [@RowID])` to mark visible rows as 1, then use `FILTER` on the original table to pull only those rows. That gets you a dynamic, filter-aware table. It is not intuitive. It requires understanding how SUBTOTAL interacts with hidden rows versus filtered rows, and it forces the user to manage an extra column they did not ask for.
Our opinion is plain: this should be simpler. The user's frustration is valid. They are not asking for a macro or a pivot table. They want the spreadsheet to respect its own filters when creating a summary. Microsoft 365 has made strides with dynamic arrays and the FILTER function, but the gap between "filtered view" and "filtered table output" remains a stumbling block. The solution exists, but it demands a level of formula construction that most users should not need to learn just to finish a task.
If you are in this position today, the clearest path forward is the FILTER + SUBTOTAL helper column method. It works. It updates automatically when you change slicers. It is not elegant, but it is dependable. And if you are building workflows like this regularly, it is worth asking whether a tool designed for static tables is the right foundation for dynamic summaries. The user's question is a symptom of a larger mismatch: the data is alive, but the tool still treats summaries as snapshots. That is the real problem worth solving.