Forum Discussion
JSON integer is too large or small error
Hi All -
I am looking for help with a Power Query error on an existing report that has refreshed in PowerBI desktop perfectly fine until this morning. The resulting error is as follows.
"JSON integer 4294967295 is too large or small for an Int32. Path '[25].MaxLength', line 1, position 9475."
Where do I look for the error based on the line and position given and is this in the Power Query Advanced Editor?
Is it soley limited to the 1 queries the error is referencing or could it be in one of the others and connected with lookup columns?
Should I be looking at changes within the data source?
I appreciate any help provided.
Hello, You must convert the data to int64, this can be done through power query in the following button
30 Replies
I had the same problem and I opened a ticket to solve it.
Solution: I had to uninstall the last version (june) and intall May version that is the folowing link:
If you download from that link, you are not going to have automatic actualizations.
You can check the version in "Ayuda" and then "Acerca de".
Bye,
thanks
Same problem and without any changes just start getting this error on desktop
Hello, You must convert the data to int64, this can be done through power query in the following buttonI confirm that the following has worked for me: Enter Power Qwery editing mode, select ALL the columns and click (to add the process step) the Transform>Detect Data type button. Many thanks to all
same
My data source is a MySQL db.
For me, the problem was being caused by a string field coming from a MySQL database view.
The first 1000 rows of the field were NULL, but further down the table there were values in the field.
The standard PowerQuery detection of the datatype for the field doesn't look beyond the first 1000 rows (it even tells you this as a comment in the footer ("Column profiling based on top 1000 rows"). So if they are all NULL (as mine were) it gets the data type wrong, and later when you try to load the entire table you get an error.
Choosing the "Detect Data Type" option from the Transform tab, did sort the problem out for me. In my case this was only after I had added and removed columns until I found the one that was causing the issue. Only then did I find this post and realise that if I'd selected all the columns and chosen "Detect Data Type", it would have sorted it without the pain.
Hello,
I have the same problem.
Bye!
Mee too, same problem
I had the same problem. In my case, after remove blank columns, the problem was solved. I had 3 blanck columns.
To find this solution, I was removing column by column in Power Query Edition. (Removing a column and run new data load, one by one)
How many who are having this same issue had it happen in the past 2 days?
Here is another post on the issues site that mirrors mine
Sounds like it is associated with update?
https://community.powerbi.com/t5/Issues/Issue-connecting-to-MySql-database/idc-p/2586255#M81042
