Expected '$schema' property in the .pbip file to follow patterns
Power BIThe message, with the parts that change in brackets:
Expected '$schema' property in '[file]' to follow patterns: [pattern]
The .pbip file is the one Power BI Desktop opens. It names a schema in $schema, and Desktop checks the address against a pattern before it reads the report or the semantic model. An address that does not fit stops the project.
- Usually
- The $schema address points at the wrong folder
- Fix
- Open the
.pbipfile and set$schemato the address in the pattern the message prints, with a version that fits it.
How the message appears
Copied exactly from each source. A name in square brackets replaced one from someone else's project.
Expected '$schema' property in '[project name].pbip' to follow patterns: ^https://developer.microsoft.com/json-schemas/fabric/pbip/pbipProperties/1.[0-9]+.[0-9]+/schema.json$
What causes it
The $schema address points at the wrong folder
A tool wrote the address with
fabric/item/pbipPropertieswhere Power BI Desktop wantsfabric/pbip/pbipProperties. Desktop failed before it read the report or the model. The issue's author checked both addresses in a follow-up reply: the first returns 404 and the second returns 200. They say the address is the only change the file needs.Source: Cnext-eu/kairos-ontology-toolkit issue 623[1].
The Report Doctor can't detect this, because the Report Doctor does not read the.pbipfile.
The fix
Open the .pbip file and set $schema to the address in the pattern the message prints, with a version that fits it. In the quoted case that is 1.0.0.
In [project name].pbip:
"$schema": "https://developer.microsoft.com/json-schemas/fabric/item/pbipProperties/1.0.0/schema.json"Line 1: change item to pbip.
"$schema": "https://developer.microsoft.com/json-schemas/fabric/pbip/pbipProperties/1.0.0/schema.json"The Power BI Report Doctor cannot find this. It does not read the .pbip file.
Other messages that stop a project opening, by the file that causes each: Power BI Desktop can't open a PBIP.
Worth knowing
- The wrong address is an easy one to write, because the schemas of the report files use
fabric/item/in theirs.
Sources
- [1]GitHub issue: Cnext-eu/kairos-ontology-toolkit issue 623. The issue description, finding 1, and the author's follow-up reply of 2026-08-27. Read 2026-10-04.
Did this page help?
It tells us which pages to fix first.