Forum Discussion
Error on create report
Hi - thanks for the response.
I did not manage to resolve this using the legacy pbip approach with just one report.json - consistently got the failure encoded or not despite checking the json was valid and sending it preencoded or not - I think there is some hidden nuance or possibly a defect in the API.
However on moving to using the new PBIP format it worked first time and worked consistently so my issue is now resolved.
Hi Anonymous,
Happy to see you here in the Microsoft Fabric Community!
Based on my knowledge, here are the troubleshooting steps that may resolve your issue:
Ensure your JSON keys are free of trailing or leading spaces (e.g., "version " should be "version"). Use a method to trim spaces from the keys before parsing the JSON.
Maintain consistent base64 encoding/decoding across systems to prevent data corruption. Any discrepancies in encoding can cause parsing issues when transferring report data.
Verify that all sections of the report (e.g., config, filters) are well-formed and contain valid data.
The problem could also be related to specific workspace or configuration settings that differ between environments. Ensure the workspace in which you're deploying the report has the same configurations and settings as the original workspace.
Simplify the reportJson to its minimum and attempt to generate the report again. This will help identify if specific sections are causing the parsing issue.
I hope my suggestions provided valuable insights. If you have any further questions, feel free to reach out to us.
If this post helped, please mark it as "Accept as Solution" so others can benefit as well.
Best regards,
Sahasra.
Hi - thanks for the response.
I did not manage to resolve this using the legacy pbip approach with just one report.json - consistently got the failure encoded or not despite checking the json was valid and sending it preencoded or not - I think there is some hidden nuance or possibly a defect in the API.
However on moving to using the new PBIP format it worked first time and worked consistently so my issue is now resolved.
Hi Anonymous,
I'm glad you found a solution and resloved the query. Thank you very much for sharing here.
Kindly mark your reply as the accepted solution so that others in the community can find it quickly.
Thankyou for connecting with Microsoft Community Forum.