Power BI error reference
Power BIMessages Power BI Desktop shows for a PBIP project, and what Fabric Git sync says about one. Each page has the exact message, the causes its sources support, a broken sample and the fix.
The .pbip file1
TMDL files4
- TMDL Format ErrorPower BI Desktop read a
.tmdlfile in the project and found something it does not accept. - TMDL Format Error: Invalid indentation was detected!TMDL reads the lines under an object declaration as that object's properties.
- Column '[name]' in table '[table]' cannot be found or may not be used in this expressionA DAX expression in the model names a column that Power BI cannot find in that table.
- The value for '[name]' cannot be determinedA DAX expression names something in square brackets, and Power BI cannot get a value for it.
The semantic model5
- Multiple SaveChanges without transactionPower BI Desktop stopped while it loaded the semantic model of a PBIP project and showed no file or line.
- Tabular databases do not support CompatibilityLevel downgradePower BI Desktop compared the compatibility level in the project with the level of a model it already holds locally, and the project asked for a lower one.
- Failed to move the data reader to the next rowA visual asked the model for data, and the query failed.
- This file uses multiple data sourcesPower BI Desktop asks this when it opens a file that reads from more than one data source.
- Field list item has errorPower BI shows this as a warning triangle beside an item in the Data pane.
Report and project JSON files7
- Something's wrong with one or more fieldsA visual refers to a field, and the model has no field by that name and of that kind.
- Required properties are missing from objectA file in the report's
definitionfolder has an object without a property its schema requires. - The /$schema property in report.json must be provided as a constEvery PBIR file names the schema version it follows in
$schema. - Can't resolve schema '[version]' in 'report.json'The report inside the file names a schema version that this Power BI Desktop does not know.
- Values for the 'pageBinding.name' property must be uniqueA page's
page.jsoncan carry apageBinding, which drillthrough and page tooltips use. - Property has not been defined and the schema does not allow additional propertiesPower BI Desktop, or a Fabric import, read a project file and found a property its schema for that file does not have.
- An additional property '[name]' was included in the [path] propertyPower BI Desktop opened the report and checked each file against its schema.
DAX queries1
Publishing to the service1
Fabric Git sync2
How these pages are written
A message is listed only when it can be quoted from a source: Microsoft Learn, the Microsoft Fabric community forum, a public GitHub issue or README, or our own run of Power BI Desktop on open data. Each quote names its source and the date it was read or seen. Where a quote held a name from someone else's project, the name is replaced with a label in square brackets, and the quote says so. A cause is listed only when its source supports it.
Written by Vishnu Shankar.
Check a project instead
The Power BI Report Doctor reads a PBIP folder or .zip in your browser and lists the file and line to fix. Each page here says whether it finds that error. Nothing is uploaded.
For how a project is laid out and what to keep in Git, see the Power BI project guides.