Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Hi,
I am trying to transform some data using the function Json.Document in Power Query.
I am getting an error when parsing the content of row 51.
Here is the image of the error.
I investigated the JSON of row 51 and found no problem with the JSON.
Hence I deleted the first 45 rows of the table (row 51 bacome row 6) and try to parse the content again.
Row 6 was now parsed correctly.
Are there limits in the Json.Document function that make this behavior understandable? Is there a way to avoid the first error?
Solved! Go to Solution.
I solved the problem reducing the lenght of the json that I was importing in Power Query.
It looks like that the json get automaticcaly truncated by the funtion josn.document, if is too long.
I did not understand the rule of truncation.
I would like to add some details:
- I am using an ODBC connector to pull data from Mongo DB
- the JSON I am trying to parse is automatically generated from a view of Mongo DB
- The view contains 68 elements and I get an error only on the element 51
- I did not find any error on the JSON of the position 51
- I deleted the first "x" rows of the dataset
- the dataset is now 68-x rows
- The data is now in position 51-x and it is parsed correctly
Can you help me explaining this behavior?
I solved the problem reducing the lenght of the json that I was importing in Power Query.
It looks like that the json get automaticcaly truncated by the funtion josn.document, if is too long.
I did not understand the rule of truncation.
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
Check out the November 2025 Power BI update to learn about new features.