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

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
OJ
Regular Visitor

Error returned: OLE DB or ODBC error: [DataFormat.Error] We couldnt convert to Number

Hi All,

 

may I kindly ask you for your help?

I am getting this error message:

"Failed to save modifications to the server. Error returned: OLE DB or ODBC error: [DataFormat.Error] We couldnt convert to Number"

 

There are only few columns containing only text and then 1 column with date and 1 column with forecast number. There are around 10 exactly same excel files differing only with forecasts numbers as the time goes. I have changed last 2 columns also to text (so everything is text) but it didn't help. Any suggestions how to fix this?

 

Thank you in advance!

1 ACCEPTED SOLUTION
v-piga-msft
Resident Rockstar
Resident Rockstar

Hi @OJ,

 

What is your data source and when do you get this error?

 

In addition, you could have a reference of the similar thread from the links below.

 

https://community.powerbi.com/t5/Desktop/DataFormat-error-We-couldnt-convert-to-Number/td-p/61492

https://community.powerbi.com/t5/Desktop/Error-DataFormat-Error-We-couldn-t-convert-to-Number-Detail...

 

Best  Regards,

Cherry

Community Support Team _ Cherry Gao
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

5 REPLIES 5
TrevorC
Advocate I
Advocate I

I had this same error. It was due to the combination of date formatting and regional settings. ie 11/30/2021 vs 30/11/2021.

I am troubleshooting a join that uses fuzzy logic. It is giving me an error when I publish it to the service. When I do I get the error "Unable to load language information for LocaleId 4105." I copied my queries into another file and changed the regional settings to see if that would address the issue. I didn't think that the interpretation of dates would be an issue but it is. In Canada we allow all possible date formats (insert eyeroll) and changing the locale to the US locks it down and led to this error.

v-piga-msft
Resident Rockstar
Resident Rockstar

Hi @OJ,

 

What is your data source and when do you get this error?

 

In addition, you could have a reference of the similar thread from the links below.

 

https://community.powerbi.com/t5/Desktop/DataFormat-error-We-couldnt-convert-to-Number/td-p/61492

https://community.powerbi.com/t5/Desktop/Error-DataFormat-Error-We-couldn-t-convert-to-Number-Detail...

 

Best  Regards,

Cherry

Community Support Team _ Cherry Gao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Hi Cherry,

 

Problem was with unpivot function... solved now after reading suggested discussions. Thank you very much! 🙂

Anonymous
Not applicable

Hi 

 

Could you share how you were able to solve this problem? Also having the same problem when pivoting my data

 

Thanks 🙂

Anonymous
Not applicable

I managed to solve the same problem Removing Errors before unpivoting. I changed all columns data types, then removed errors before unpitvoting and it worked 

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

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

April Fabric Community Update

Fabric Community Update - April 2024

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