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

Be one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now

Reply
Micgig
Frequent Visitor

'Input string was not in a correct format' when importing using MySQL database connector

Dear all,

 

hope you are well. Wish to thank you in advance for the help.

I have been trying to import a few tables from a database hosted on Alibaba cloud/AnalyticDB/MySQL instance, using the MySQL database connector.

Regardless of the selected tables, which look all fine to me, when importing I always face the captioned error message: 'Input string was not in a correct format'.

 

I have tried the same process importing in Tableau and it all works fine: been able to import any of the tables without issues.

Would any of you know how to solve this?

Thank you so much,

 

Michele

1 ACCEPTED SOLUTION

Hi, @Micgig 

 

Maybe it has something to do with the "Chengdu - Pmia" field in your table.

- + $ ( ) Display a literal character. To display a character other than one of those listed, precede it with a backslash () or enclose it in double quotation marks (" ").

 

The most important thing is that the "-" is for characters in numeric format. You can try replacing this string before connecting.

 

Please refer to the following document for character formatting requirements.

https://docs.microsoft.com/power-bi/create-reports/desktop-custom-format-strings 

 

Best Regards,

Community Support Team _Charlotte

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

3 REPLIES 3
amitchandak
Super User
Super User

@Micgig , can you share a sample string you have used for the connection?

Try backslash and check

Alibaba cloud\AnalyticDB\MySQL instance

 

Join us as experts from around the world come together to shape the future of data and AI!
At the Microsoft Analytics Community Conference, global leaders and influential voices are stepping up to share their knowledge and help you master the latest in Microsoft Fabric, Copilot, and Purview.
️ November 12th-14th, 2024
 Online Event
Register Here

@amitchandak 

thanks for replying.

One table, for testing purposes, literally consists of the following data (only 1 row).

 

department_iddepartment_namets
23Chengdu - Pmia202122110301001

 

I don't see particular formatting reasons why Power BI couldn't load this single row.

Yes the path is correct Alibaba cloud\AnalyticDB\MySQL instance.

What do you think?

Thanks!

 

Hi, @Micgig 

 

Maybe it has something to do with the "Chengdu - Pmia" field in your table.

- + $ ( ) Display a literal character. To display a character other than one of those listed, precede it with a backslash () or enclose it in double quotation marks (" ").

 

The most important thing is that the "-" is for characters in numeric format. You can try replacing this string before connecting.

 

Please refer to the following document for character formatting requirements.

https://docs.microsoft.com/power-bi/create-reports/desktop-custom-format-strings 

 

Best Regards,

Community Support Team _Charlotte

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!

Dec Fabric Community Survey

We want your feedback!

Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.

ArunFabCon

Microsoft Fabric Community Conference 2025

Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.

December 2024

A Year in Review - December 2024

Find out what content was popular in the Fabric community during 2024.