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

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Reply
TheBishopEmpire
Frequent Visitor

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".

 

TheBishopEmpire_0-1668445881802.png

 

TheBishopEmpire_1-1668445908741.png

 

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

1 ACCEPTED SOLUTION

@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. 

View solution in original post

2 REPLIES 2
v-yalanwu-msft
Community Support
Community Support

Hi, @TheBishopEmpire ;

 

You could change type to Date/Time;

1. add custom column.

vyalanwumsft_0-1668501925881.png

2.change type.

vyalanwumsft_1-1668502083589.png


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

@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. 

Helpful resources

Announcements
Europe Fabric Conference

Europe’s largest Microsoft Fabric Community Conference

Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.

Power BI Carousel June 2024

Power BI Monthly Update - June 2024

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

PBI_Carousel_NL_June

Fabric Community Update - June 2024

Get the latest Fabric updates from Build 2024, key Skills Challenge voucher deadlines, top blogs, forum posts, and product ideas.

Top Solution Authors
Top Kudoed Authors