Forum Discussion
How to identify which column is causing OLE DB or ODBC error: [DataFormat.Error] We couldn't convert
I have many columns in my table. Data source is a sql server table. After a number of applied steps when I press "Close and apply", Power BI desktop prompt me OLE DB or ODBC error: [DataFormat.Error] We couldn't convert. How could I identify which column is causing this issue without delete my applied steps one by one?
3 Replies
- Chakravarthy
Resolver II
Anonymous , Open Power Query, click on Source step follwed by ramining steps, click on Step-by-Step in Applied Steps in right side. If you see the table each and every step, then that step is not having issue. Mostly, You can will see the issue in Changed Type or Custom Columns
- AnonymousNot applicable
Thanks for quick reply.
I can see the table in every step. The error only occur when I press "Apply" or "Close & Apply".
- AnonymousNot applicable
Hi Anonymous ,
Here's a step-by-step plan to troubleshoot the issue:
1. Check Data Types: Ensure that the data types in Power BI match the data types in the data source. Data type mismatches are common causes of such errors.
2. Binary Search Method:
- Duplicate the query causing the error.
- Use a binary search approach by removing half of the columns and then applying the changes. If the error persists, the issue is within the remaining columns. If not, the issue was in the removed half.
- Repeat this process by halving the number of columns until you isolate the problematic column.3. Use the Query Diagnostics:
- In the query editor, go to the "Tools" tab.
- Click on "Query Diagnostics" to start a diagnostics session.
- This can help you identify which step is causing the issue.Best regards,
Community Support Team_Binbin Yu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.