Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowJuly 7 - July 17 | Round 2 of the Power BI Dataviz World Championships. Don't miss your chance! 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.
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
Join Fabric Data Days 2026: 60 days of free live/on-demand sessions, challenges, study groups, and certification opportunities.