Power BI Report Doctor
Power BIDrop 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.
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.
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. TMDL property names are not checked against the language, and a byte order mark at the start of a TMDL file is not reported. It cannot know which schema versions your Power BI Desktop accepts. The older report.json format is reported but not read.