Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us at Qlik Connect 2026 in Orlando, April 13–15: Register Here!
cancel
Showing results for 
Search instead for 
Did you mean: 
MattiaD
Contributor
Contributor

Failed to read data at {0:26}

Buongiorno a tutti, 

ho creato una connessione ad un db MySql nella versione SaaS di QlikSense. Riscontro il seguente problema, quando provo a selezionare una tabella nello script mi viene restituito il seguente errore:

MattiaD_0-1670939593070.png

Questo succede SOLO per questa tabella, le altre presenti nel database sono state aggiunte allo script senza errori o problemi.

Non riesco a capire quale sia il problema, potete aiutarmi?

Grazie mille

Labels (2)
5 Replies
rhodamineb1
Contributor II
Contributor II

Hi, 

 

I have the exact same issue on few tables. I'd appreciate any help.

 

Thanks.

Daniele_Purrone
Support
Support

Buon pomeriggio Mattia!
This might happen if the tables contain unsupported data types (like json, for instance).

The list of supported data types is here:
Supported MySQL Enterprise Edition data types

Hope this helps!

Daniele - Principal Technical Support Engineer & SaaS Support Coordinator at Qlik
If a post helps to resolve your issue, please accept it as a Solution.
rhodamineb1
Contributor II
Contributor II

Hello,

Firstly thanks for your kind answer. I've checked my table that has been throwing error but all the field types are supported by Qlik. 

You can see my tables field types below:

 

rhodamineb1_0-1673442552709.png

 

Daniele_Purrone
Support
Support

Thanks @rhodamineb1 is that also related to MySQl? Are the same tables always failing consistently? 
If you try loading them from a version of Qlik Sense Desktop, are they also failing?

Daniele - Principal Technical Support Engineer & SaaS Support Coordinator at Qlik
If a post helps to resolve your issue, please accept it as a Solution.
NicolasAimain1
Partner - Contributor III
Partner - Contributor III

For those who encounter this problem, one solution is to convert data on SQL side

I had the same problem on several field but it worked when I excluded these fields or limited the amount of row loaded

I manage to load the full dataset using CONVERT(<my_field>,CHAR) as <my_field> during the SELECT on each field that had an error

Regards