Forum Discussion
🚨 PBIR Format Enabled in the Preview features but Still Getting Error? What Am I Missing
- 4 months ago
Hi Mesalome
This should work outside of demos, but the most likely issue is that enabling the preview feature alone does not automatically convert an existing PBIP report into PBIR.
For an existing project, Power BI Desktop still has to perform the upgrade itself. According to Microsoft’s documentation, after enabling the PBIR preview feature, the PBIP needs to be opened in Desktop, saved, and then upgraded so the report is converted from the legacy single report.json structure into the PBIR definition\ structure.
https://learn.microsoft.com/en-us/power-bi/developer/projects/projects-report
So if the JSON was edited manually and the files now look like PBIR, but Desktop never actually completed the conversion, that would explain the error message. Microsoft also states that PBIR can be created or converted by using Power BI Desktop, not just by manually rearranging or editing files.
https://learn.microsoft.com/en-us/power-bi/developer/embedded/projects-enhanced-report-format
A few things to check:
Confirm the project was actually upgraded, not just that the preview option was enabled. Existing PBIPs are not converted automatically.
Check the report folder structure. PBIR-Legacy uses a single report.json, while PBIR uses a definition\ folder with separate files for pages, visuals, bookmarks, and related metadata.
Check the definition.pbir version. Version 1.0 supports PBIR-Legacy only, while version 4.0 or higher supports the PBIR definition\ folder format.
If any PBIR files or folders were renamed manually, restart Power BI Desktop before reopening the project.Reference:
https://learn.microsoft.com/en-us/power-bi/developer/projects/projects-reportSo the likely missing piece is not the JSON edit itself, but that the report was never fully upgraded by Desktop into PBIR format.
And yes, this is supported beyond demos. Microsoft explicitly describes PBIR as enabling manual or programmatic batch changes to report files, so this is a documented scenario, not just something shown in internal examples.
https://learn.microsoft.com/en-us/power-bi/developer/embedded/projects-enhanced-report-format
If none of that helps, it may also be worth testing with a brand-new PBIP created after the preview feature is enabled. That is usually the fastest way to tell whether the issue is with the current project’s conversion path or with the local Desktop environment.
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
Hi Mesalome
This should work outside of demos, but the most likely issue is that enabling the preview feature alone does not automatically convert an existing PBIP report into PBIR.
For an existing project, Power BI Desktop still has to perform the upgrade itself. According to Microsoft’s documentation, after enabling the PBIR preview feature, the PBIP needs to be opened in Desktop, saved, and then upgraded so the report is converted from the legacy single report.json structure into the PBIR definition\ structure.
https://learn.microsoft.com/en-us/power-bi/developer/projects/projects-report
So if the JSON was edited manually and the files now look like PBIR, but Desktop never actually completed the conversion, that would explain the error message. Microsoft also states that PBIR can be created or converted by using Power BI Desktop, not just by manually rearranging or editing files.
https://learn.microsoft.com/en-us/power-bi/developer/embedded/projects-enhanced-report-format
A few things to check:
Confirm the project was actually upgraded, not just that the preview option was enabled. Existing PBIPs are not converted automatically.
Check the report folder structure. PBIR-Legacy uses a single report.json, while PBIR uses a definition\ folder with separate files for pages, visuals, bookmarks, and related metadata.
Check the definition.pbir version. Version 1.0 supports PBIR-Legacy only, while version 4.0 or higher supports the PBIR definition\ folder format.
If any PBIR files or folders were renamed manually, restart Power BI Desktop before reopening the project.
Reference:
https://learn.microsoft.com/en-us/power-bi/developer/projects/projects-report
So the likely missing piece is not the JSON edit itself, but that the report was never fully upgraded by Desktop into PBIR format.
And yes, this is supported beyond demos. Microsoft explicitly describes PBIR as enabling manual or programmatic batch changes to report files, so this is a documented scenario, not just something shown in internal examples.
https://learn.microsoft.com/en-us/power-bi/developer/embedded/projects-enhanced-report-format
If none of that helps, it may also be worth testing with a brand-new PBIP created after the preview feature is enabled. That is usually the fastest way to tell whether the issue is with the current project’s conversion path or with the local Desktop environment.
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
- Mesalome4 months agoFrequent Visitor
I discovered that an older version of Microsoft Power BI Desktop was still affecting my environment. I fully uninstalled it, cleared the local cache, and then installed the latest version.
After that, I carefully enabled the preview features step by step (with restarts in between): first “Save as PBIP,” then “Save as PBIR.” I then re-saved the report as a PBIP, and the new PBIR folder structure was generated correctly.
Following this, I was able to modify the TMDL/script files, and the changes were successfully reflected in the report.
Can't be happier. Thank you.