Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Reply
dgw_REA
Frequent Visitor

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.

1 ACCEPTED SOLUTION

Hello,

You must convert the data to int64, this can be done through power query in the following button

Powerjemarr123_0-1655491404161.png

 

 

 

View solution in original post

30 REPLIES 30
Ai_
New Member

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.

 

Venu_Malladi
New Member

Worked for me!
Appreciate the help @dgw_REA!

julienvdc
Helper III
Helper III

same here... the fix "detect data type" does not work....

Hi
Did you chosse all columns when you did "detect data type" in all tables ? 

yes

Ah! Indeed, I might have missed the "select-all", thanks for that.

 

I did it for each of my tables; select-all columns --> "detect data type". Next data refresh and the issue seems to be gone. 😄

ake
Frequent Visitor

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:

 

https://docs.microsoft.com/en-us/power-bi/fundamentals/desktop-latest-update-archive?tabs=powerbi-de...

 

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".

 

ake_0-1655905646345.png

 

ake_1-1655905716791.png

 

Bye,

martigas
Frequent Visitor

thanks

Hagen941
New Member

Same here, bye

dgw_REA
Frequent Visitor

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

dgw_REA
Frequent Visitor

My data source is a MySQL db.

dgw_REA
Frequent Visitor

How many who are having this same issue had it happen in the past 2 days?

I got the error just today 

.....I saw there was a June update for PBI and wondering if this is a contributing factor.

 

Could be this ..... as the error is weird 

Caltabiano
New Member

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)

Does not work for me 

issue is that I can't understand where is the issue as can't see what is the field the message relates ..... 

good thought, this does not help my situation though (no blank columns) but it might help others. Thanks for contributing.

Anonymous
Not applicable

same problem here, try to load data and the problem occurs

 

pmargari
Advocate II
Advocate II

Same problem and without any changes just start getting this error on desktop 

 

Helpful resources

Announcements
July 2024 Power BI Update

Power BI Monthly Update - July 2024

Check out the July 2024 Power BI update to learn about new features.

July Newsletter

Fabric Community Update - July 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors
Top Kudoed Authors