OLE DB or ODBC error: Type mismatch. (Exception from HRESULT: 0x80020005 (DISP_E_TYPEMISMATCH))

[Subodh-2025]

Dear All,

I am getting following error which I am not able to understaqnd.. My data is in Sharepoint list and I have not chenaged anything with regards to type etc.

OLE DB or ODBC error: Type mismatch. (Exception from HRESULT: 0x80020005 (DISP_E_TYPEMISMATCH))

Kindly support.

Regards

Subodh

[v-tejrama]

Hi @Subodh-2025 ,

Thank you @Shahid12523 and @grazitti_sapna  for the response provided!

Has your issue been resolved? If the response provided by the community member addressed your query, could you please confirm? It helps us ensure that the solutions provided are effective and beneficial for everyone.

Thank you for your understanding!

[v-tejrama]

Hi  @Subodh-2025 ,

I wanted to follow up and see if you had a chance to review the information shared. If you have any further questions or need additional assistance, feel free to reach out.

Thank you,

Tejaswi.

[v-tejrama]

Hi  @Subodh-2025 ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank you,

Tejaswi.

[Shahid12523]

This error means a column in your SharePoint list is returning mixed/invalid types.

Causes:

Choice/Lookup/Person fields (sometimes return text, sometimes records/tables).

Nulls or mixed text/number values.

SharePoint schema change.

Fix:

In Power Query, check column types.

Use safe conversion, e.g.

try Number.FromText([Column]) otherwise null

For multi-select Choice/Lookup → expand to text with Text.Combine().

Usually caused by Choice/Lookup fields with multiple values.

[grazitti_sapna · Accepted solution]

Hi @Subodh-2025 

This error is usually caused by mixed data types or unexpected values in your SharePoint List, even if you haven't changed column types in Power Query or on SharePoint.

Troublshooting Steps:

• Open Power Query Editor in Power BI. Explicitly set the data type for each column (right-click column → Change Type), and move these steps to the top of the applied steps list.
• Check for unexpected or blank values. Even a single blank, null, or non-typed entry (e.g., text in number/date columns) can cause this error.
• Review SharePoint field configurations. If your numeric/date columns are set as "Single line of text" in SharePoint, convert them to actual Number/Date types for reliable refreshes.
• If the issue persists, try removing and reconnecting the SharePoint source to force Power BI to redetect field types

If that's not enough, create a clean copy of the query/table and incrementally rebuild type logic, checking for the exact step where the type mismatch first appears.

🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.

💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.

🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.

🔗 Curious to explore more? [Discover here].

Let’s keep building smarter solutions together!