-
Notifications
You must be signed in to change notification settings - Fork 205
Power BI Report Templates for Storage Account not opening #1971
Copy link
Copy link
Open
Labels
Needs: Attention 👋Issue or PR needs to be reviewed by the author or it will be closed due to no activityIssue or PR needs to be reviewed by the author or it will be closed due to no activitySkill: DeploymentResource deployment automation via bicep or terraformResource deployment automation via bicep or terraformStatus: 📋 Pending confirmationWaiting on explicit confirmation that the issue was resolved in previous releaseWaiting on explicit confirmation that the issue was resolved in previous releaseTool: Power BIPower BI reportsPower BI reports
Description
Metadata
Metadata
Assignees
Labels
Needs: Attention 👋Issue or PR needs to be reviewed by the author or it will be closed due to no activityIssue or PR needs to be reviewed by the author or it will be closed due to no activitySkill: DeploymentResource deployment automation via bicep or terraformResource deployment automation via bicep or terraformStatus: 📋 Pending confirmationWaiting on explicit confirmation that the issue was resolved in previous releaseWaiting on explicit confirmation that the issue was resolved in previous releaseTool: Power BIPower BI reportsPower BI reports
🐛 Problem
TODO: Add a clear and concise description of what the bug is.
When attempting to open a Power BI Template (.pbit) file, the application fails with error "Cannot de-serialize Database. The JSON input is not properly formed." Upon inspection, the DataModelSchema file within the .pbit package contains only the value "null" instead of valid JSON, causing the deserialization to fail at line 1, position 4. This appears to be a file corruption issue that occurred during the template creation or save process.
👣 Repro steps
TODO: Add repro steps below:
Download the report zip file, expand the zip file and try to open any of the reports
🤔 Error
Upon inspection, the DataModelSchema file within the .pbit package contains only the value "null" instead of valid JSON, causing the deserialization to fail at line 1, position 4.