Forum Discussion
Fabric Rest API Create Report Report.Json Error
Hi Anonymous,
Thanks for reaching out to the Microsoft fabric community forum.
It looks like that the issue lies in the incorrect JSON formatting within the "reportJson" string. Specifically, the keys and values inside the config and filters fields are not properly escaped, which is causing the parsing error. The reportJson string contains extra spaces after the keys This could be breaking the JSON parser. Also there can be
Encoding/Decoding Issues. If the JSON is stored in an encoded format (e.g., Base64), ensure it is properly decoded before use. If it is already in plain text, check for any double encoding or unintended escape characters.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support TeamIf this post helps then please mark it as a solution, so that other members find it more quickly.
Thank you.
Hi Anonymous,
Thanks for reaching out to the Microsoft fabric community forum.
It looks like that the issue lies in the incorrect JSON formatting within the "reportJson" string. Specifically, the keys and values inside the config and filters fields are not properly escaped, which is causing the parsing error. The reportJson string contains extra spaces after the keys This could be breaking the JSON parser. Also there can be
Encoding/Decoding Issues. If the JSON is stored in an encoded format (e.g., Base64), ensure it is properly decoded before use. If it is already in plain text, check for any double encoding or unintended escape characters.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support Team
If this post helps then please mark it as a solution, so that other members find it more quickly.
Thank you.
Hi Anonymous,
As we haven’t heard back from you, so just following up to our previous message. I'd like to confirm if you've successfully resolved this issue or if you need further help.
If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. If you find a reply particularly helpful to you, you can also mark it as a solution.
If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.
Thank you for your patience and look forward to hearing from you.
Hi Anonymous,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution so that other community members can find it easily.
Thank you.Hi Anonymous,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.