Power BI Report Doctor
Power BIBetaNothing is uploadedDrop a Power BI project folder or .zip to find the file and line to fix, or paste an error from Power BI Desktop. It runs in your browser.
- Save as PBIPSave the project as .pbip with the PBIR report format turned on. The older report.json format is not read.
- Drop the folder, or paste the errorDrop the whole project folder. A report is checked against its model only when both are there.
- Fix the file and lineEach finding names the file, the line and the fix. Nothing is uploaded.
If Power BI Desktop says "Multiple SaveChanges without transaction" or "Tabular databases do not support CompatibilityLevel downgrade", the cause may be a stale cache.abf under .pbi. That file is never read here. Close Power BI Desktop, delete it and open the project again.
Drop a Power BI project folder or a .zip here
The folder that holds your .Report and .SemanticModel folders. Only the report and model definition files are read.
What it checks
| Check | What it looks at |
|---|---|
| Field references | Every field a visual uses, matched against the model, and whether it is a column or a measure there. |
| DAX references | Every name the DAX uses, matched against the model: in measures, calculated columns and tables, calculation items, KPIs, format strings and role filters. |
| Schema | Each report file against the Microsoft schema it declares, with the line. |
| TMDL and unreadable files | Model lines that cannot be read, and files that would not open. |
| Pages | Two pages with the same page binding name, which Power BI Desktop reports as an error. |
| Pasted errors | A Power BI Desktop message matched against 21 messages with sources. |
See where each number comes from
Power BI Studio opens the same project and draws each page with made-up values. Click a visual to follow it to its calculations, data tables and sources. Open Power BI Studio
When the error message is the confusing part
A Power BI Desktop message names a file and a line at best, and sometimes neither. Paste it under Paste an error, with any detail lines, and you get the causes its sources support. Causes your text points to come first. The Power BI error reference has each one with its sources, a broken sample and the fix.
Schema-valid is not the same as correct
Every PBIR file names a public JSON schema. A file can pass its schema and still point at a column the model no longer has. The schema checks shape. It cannot know that a visual asks for a field that was renamed last week. This checks both: each file against the schema it declares, and every field a visual uses against the model.
Nothing you drop is uploaded
A report folder holds table names, server names and sometimes client data. Your browser reads the files and runs every check itself. There is no upload step. Only the report and model definition files are opened. Cache and local settings files are listed by name and never read. Tests that watch the network on this page fail if a file's content is sent anywhere.
What it does not check yet
Slicer defaults, filter settings, and how a report differs between Power BI Desktop and the Power BI service. Nothing in a TMDL file is checked against the language: not property names, indentation under an object, comment placement or how a role filter is written. DAX is checked only for names the model does not have, not for its syntax or its functions. A byte order mark at the start of a TMDL file is not reported, and files under .pbi, such as a stale cache.abf, are never read. It cannot know which schema versions your Power BI Desktop accepts. The older report.json format is reported but not read.