You skip the visual layer entirely. You write raw DAX like TOPN(10, ALL(Product), [Sales]) , get the data, and inject it directly into a PDF template. No slicers. No broken visuals. Pure, typed data on a page.
But here’s the dirty secret of enterprise analytics: dax pdf
You can use Power Automate to run a DAX query against a Power BI dataset (using the "Run a query against a dataset" action), send the JSON result to a "Create HTML table" action, then use the "Convert HTML to PDF" connector. You skip the visual layer entirely
This returns a table of data. The PDF rendering engine then places that table onto a fixed page size (Letter/A4). This is incredibly powerful—you get pixel-perfect control—but you lose the automatic recalculation of measures across visual interactions. When moving from dashboards to documents, watch out for these three assumptions: 1. Assumption: "The visual will summarize for me" In a dashboard, a matrix visual automatically adds subtotals and grand totals based on your DAX. In a PDF (especially a standard Power BI export), what you see is what you get. If your visual doesn't show subtotals on screen, they won't magically appear in the PDF. No broken visuals
Instead of dragging "Total Sales" onto a card, you write:
In a PDF? There is no click.
In a Paginated Report, you write DAX against a DirectQuery or Import dataset, but the engine treats it like a query language, not a measure language. You can't rely on implicit measures. You have to write explicit EVALUATE and DEFINE statements.