Dynamic Pivot Tables in Power BI: Let Report Users Pivot After Publish (2026)
A report goes live and the first request arrives: can I see this by year instead of by region? In Excel that is a drag. In a published Power BI report, the Matrix layout was set by whoever built it, so the answer is often a ticket. This guide covers three ways to let report viewers pivot a published report themselves, what each one keeps, who owns the view it creates, and where each one stops.

1. Why the Matrix is locked after publish
The Matrix is Power BI's closest built-in match for a pivot table. It supports rows, columns and values, and it handles hierarchies and drill-down well. The catch is where the layout lives. Field wells belong to the report definition, which the author edits in Power BI Desktop or in edit mode in the service. A viewer opens the published report in reading view, where those wells are not available.
In Excel, a pivot table is an exploration tool. In a published report, the Matrix is a presentation tool: polished, consistent and controlled by the author. Both are valid. The friction starts when the same table has to answer a different question.
What a published Matrix does
The words "by default" matter. If the author turns on Personalize visuals, viewers can swap fields themselves. That is covered in the next section.
2. Three ways to let viewers pivot a published report
These are not rivals. Each fits a different kind of question, and they can sit in the same report.
| Bookmarks | Personalize visuals | Pivot inside the visual (Flexa Tables) | |
|---|---|---|---|
| What it keeps | Filters, slicers, sort and drill state, captured as a snapshot of the whole page. | The viewer's changes to a visual: the visualization type and the fields in Rows, Columns and Values. | Pivot structure, formulas, conditional formatting, filters, sort order and hidden columns, saved as layouts inside the visual. |
| Who owns the view | The author creates the report bookmarks. Viewers can switch between them and can save personal bookmarks in the Power BI service. | The viewer. The author decides whether the feature is on. | The author sets a default layout, for example one per audience. Viewers with a license key can add their own. |
| Where it stops | A bookmark restores a state that already exists. A new arrangement of fields has to be built first, often as a duplicate page. | It reshapes a standard visual. It does not add table features the visual lacks, and it depends on the visuals and the embedding setup Microsoft supports. | It is a custom visual, so it has to be added from AppSource. Viewers work with the fields the author put in the visual, up to five layouts per visual. |
Way 1
Bookmarks
Bookmarks are built into Power BI and need no extra visual. An author arranges the page, saves the state and adds a bookmark. The Bookmarks pane has two sections: Report bookmarks, which the author builds, and Personal bookmarks, which viewers save for themselves. Bookmarks work well for a small set of known views, such as a Summary and a Detail version of the same page.
The limit is that a bookmark switches to something that was already built. If a viewer wants a table arranged in a way nobody prepared, the author has to create that arrangement first, and every extra view tends to mean another visual or another page.

Way 2
Personalize visuals
Personalize visuals is a real Power BI feature, and for many reports it is enough. When the author enables it, viewers get a personalize option on the visual in the Power BI service. The Personalize pane lists the visualization type and the fields in Rows, Columns and Values, each with an option to add a field, so a viewer can restructure a Matrix without editing the report. A reset icon at the top of the pane undoes the changes.
The trade-offs are practical. The author has to switch it on, and the changes belong to the viewer rather than to a view the whole team can open. It also reshapes a standard visual, so it does not add table behaviour the visual does not already have. Check Microsoft's documentation for the visuals and embedding scenarios it supports.

Way 3
Pivot inside the visual with Flexa Tables
This approach moves the pivot into the visual. The footer of the visual has a Pivot button next to Export data, Chart, Conditional, Manage and Analytics. Viewers use it to rearrange fields across Rows, Columns and Values in the published report, and the table restructures in place. The author does not edit the report, and the rest of the page stays as it is.
A layout saves a table's setup inside the visual. Each one keeps:
A visual holds up to five layouts. Changes save automatically, there is no Save button, and switching applies the snapshot almost instantly. The author can build one layout per audience, for example an executive summary and an analyst detail view, and set one as the default. Viewers with a license key can add their own.

Write a Rows or Columns formula once against child names, and Flexa Tables repeats it under every parent at that level, calculated from that parent's own children. A parent that is missing one of the children shows a blank rather than a misleading 0.
A switch named Include in parent & Total carries a Rows formula into each parent subtotal and the Grand Total. It starts off for new formulas. In the formula editor, fields are inserted by clicking them.
Add Flexa Tables from Microsoft AppSource and test it on your own Power BI data.
Start free trial →3. Prepare the report before you publish
Viewers can rearrange what is in the visual, so the preparation happens before you publish.
4. Month-over-month variance, in short
Period comparison is the request that follows a pivot.
Setup and variance options are covered on the Power BI pivot table page.
5. Where viewers pivot on their own
Any report that gets a follow-up question after publish is a candidate. These are the common cases.
6. FAQ
Personalize visuals lets a report viewer change a visual in the Power BI service without editing the report. The Personalize pane shows the visualization type and the fields in Rows, Columns and Values, and the viewer can change them and reset the visual. The report author turns the feature on.
A bookmark captures the state of a whole report page, including filters, slicers and which visuals are showing. A layout in Flexa Tables lives inside the visual and saves the table's own setup, such as pivot structure, formulas, filters and sort order, so the rest of the page stays as it is.
No. Viewers work in the browser or the Power BI app. The author sets up the visual and the fields in Power BI Desktop before publishing, and the viewer pivots from the published report.
With a standard Matrix, a viewer can expand and collapse groups, drill along the hierarchies the author defined and use slicers, but cannot swap rows and columns. An in-visual pivot such as Flexa Tables adds that step inside the visual itself.
