Forum Discussion
Helper IVWe found extra characters at the end of JSON input.
Advocate III've had a similar issue before. In our case, the input was actually JSONL (json lines or something), and it was basically missing start and end braces around the full json content, as well as commas at the end of each line, to parse it as an array of json objects. Not sure if you're problem is the same, but it might be something along the same lines -> valid json, just not wrapped together properly.
Hope that leads you in the right direction :)
Helper IVNope, it's regular JSON. And it validates with every tool that I've thrown it at. Does Power BI have some "special" JSON needs?
- intrasight
I noticed that the section of JSON containing the data table had no line breaks between rows. After adding line breaks, I no longer get the above error message. This leads me to believe that a) there is some limitation in the JSON parser used by Power BI, and b) this limitation manifests itself with an incorrect error message.
I am seeing the same error and the json being returned by the API is valid. How did you add the line breaks?
- intrasight
I would download the JSON from that API and then serve it from your own web app to figure out what are the needed changes. Then make your web app a proxy to the API and make those changes on the fly to the response.
