Forum Discussion

TheBishopEmpire's avatar
TheBishopEmpire
Frequent Visitor
3 years ago
Solved

OLE DB or ODBC error: type mismatch (exception from HRESULT: 0x80020005 (DISP_E_TYPEMISMATCH))

I was receiving this error when converting DateTime to DateTimeZone using a Dataverse data source. I could not find any other posts here in the community regarding a work around or fix. I thought I would share my solution. 

 

Scenario: 
I simply needed to converty the dataverse field "createdon" from DateTime to DateTimeZone and ultimately into a Local TimeZone for the end user. 

 

Steps: 
1. Added a new column called "createdon_UTC" from "createdon". PowerQuery will create this as a text type. 

2. Change the type to DateTimeZone on "createdon_UTC".

3. Added a new column called "createdon_Local" from "createdon_UTC". PowerQuery will create this as a text type. 

4. Change the type to DateTimeZone on "createdon_Local".

 

 

 

Be sure to like this post if you've found it to be a solution for you. 

  • TheBishopEmpire's avatar
    TheBishopEmpire
    3 years ago

    v-yalanwu-msft Power Query already had DateTime as the type for "createdon". Unfortunately, I needed to add timezone in order for the UTC to Eastern-US convesion for my users. Once I made that change, before my final solution posted here, Power Query would not apply the changes. This is when the error would appear. 

2 Replies

    • TheBishopEmpire's avatar
      TheBishopEmpire
      Frequent Visitor

      v-yalanwu-msft Power Query already had DateTime as the type for "createdon". Unfortunately, I needed to add timezone in order for the UTC to Eastern-US convesion for my users. Once I made that change, before my final solution posted here, Power Query would not apply the changes. This is when the error would appear.