Skip to content

No account required

Start a project

Turning a Power BI report into a presentation without screenshotting it.

A dashboard is built for monitoring and a meeting needs an argument. The move between them starts from the data model, not from the screen.

  • Read6 min
  • Sections4

How do I turn a Power BI report into a presentation?

Start from the data model inside the .pbix rather than from screenshots. A .pbix is a ZIP holding the imported tables and the DAX measures, and both can be read without Power BI installed. Rebuild the handful of figures the meeting needs as slides with one claim each, using the measure definitions as written rather than re-deriving them. The exception is a DirectQuery report, which contains the schema and measures but no rows.

01

Slides and dashboards answer different questions

A dashboard exists to be checked repeatedly: it shows the current state of many things at once and lets the viewer explore. A presentation exists to be walked through once, in order, toward a decision — and a screenful of tiles pasted onto a slide asks the room to do the exploring the author was supposed to have done.

The test for which you need is whether there is a decision at the end. A meeting deciding something needs a sequence of claims with evidence under each; a team keeping an eye on something needs the dashboard it already has.

02

The report file contains more than the report

A .pbix is a ZIP container. Inside it sit the report layout, the tables that were imported, and the DAX measures defined on top of them — and the tables and measures can be read directly, without Power BI installed.

The measures are the part people forget to take. A measure named Margin is somebody's decision about what margin means in this business, written down and used in production. Carrying that definition into the deck, as it was written, is what keeps the slide's number consistent with the report it came from.

Two measures called Revenue in the same model routinely compute different things. The expression, not the name, is the definition.

03

What carries over, and what does not

The data and the definitions carry. The visuals do not, and should not: a chart designed to be explored interactively is rarely the chart that makes a point on a slide, and slicers, drill-downs and tooltips have no meaning on paper.

What also does not carry is anything the file never contained. A report in DirectQuery mode holds the schema and the measures but no rows — it queries a warehouse at render time — so the numbers on screen are not in the file, and a .pbit template is the same situation by design. That is worth discovering before the meeting rather than during it.

04

Build the deck as claims, not as pages

One claim per slide, with the figure that supports it and the definition it was computed under. A slide titled "Q3 performance" is a page; a slide titled "Margin fell, and it fell in one product line" is a claim someone can disagree with, which is the point of the meeting.

Sort any category chart by value, mark a final period that is incomplete as incomplete, and keep the number of slides close to the number of decisions. Everything cut can live in an appendix, which is where a dashboard's completeness belongs in a meeting.

This is also the shape an automated pass produces from the same file: the tables analysed, the measures used as the definitions, and the result exported as a slide deck rather than as another dashboard.

See it on a real project

Contractor spend rose $412,000 while headcount spend fell $448,000, leaving only a $4,000 net change.

What actually changed between these budget versions?

Related

Try it on your own file.

Every check described here runs automatically, and your first findings arrive in full before you pay for any of it.

No account needed to start. You only pay when you like what you see.