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
eddd83
Resolver I
Resolver I

OLE DB or ODBC error: [Data.Error] We Couldn't Covert to a number

july 12 FOPMDM error full.png

 

 

My fact has many number columns and it would be extremely tedious to check them all. Why Power BI can't tell me which column is causing the problem?!?

 

Help?

1 ACCEPTED SOLUTION

for whatever reason, it didn't return a table with the errors

 

Anyhow, I was able to isolate the problematic table by playing with "enable load" on the tables appending to the fact table. I really wish power BI did a better job at identifying the problem tables. 

View solution in original post

2 REPLIES 2
MFelix
Super User
Super User

Hi @edd83,

If you make the edit of the query on the desktop version when you push on the model to the front end it returns a table with the errors normally it should be easy to get the column that as the error.

Regards,
MFelix

Regards

Miguel Félix


Did I answer your question? Mark my post as a solution!

Proud to be a Super User!

Check out my blog: Power BI em Português



for whatever reason, it didn't return a table with the errors

 

Anyhow, I was able to isolate the problematic table by playing with "enable load" on the tables appending to the fact table. I really wish power BI did a better job at identifying the problem tables. 

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.