Date fields in Custom table

(2) Share

Report

Posted on by LS-28081008-0

Has Microsoft recently changed the default behavior of Date fields in Dataverse Views / Power Query?

We have been building ETL processes that have always worked without any issues.

However, we recently noticed that fields which were previously returned as Date are now suddenly coming back as DateTime via Power Query/Power BI

Categories:

Dynamics 365 general

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

Abdul Wahab 12,106 Moderator on at

Like (0)

Report

Date fields in Custom table

1. Dataverse Stores All Dates with a Time Component (UTC)

Dataverse stores all date and time values in UTC, even if your field is set as Date Only. That means there’s always a time component—usually set to midnight (00:00:00Z)—unless the field’s behavior is “Date Only,” where the time part isn’t stored at all.
Power Query, however, will always interpret a Dataverse “Date Only” field as a DateTime because it sees the underlying timestamp.
This is intentional behavior and was documented a while ago.

2. Power Query Defaults to DateTime

Power Query/Power BI, by default, doesn't infer “Date Only” properly—it reads the metadata as including time, so it classifies the field as DateTime. That gives you a DateTime in the model even though the time is always 00:00.

This isn’t a recent change—this is how it’s always worked—but you're just noticing it now.

Abdul Wahab
Direct: +923323281237
Email: abdulwahabubit@outlook.com
LinkedIn: https://www.linkedin.com/in/abdul-wahab-a5b8b011a/
Twitter: https://twitter.com/Abdulwahabubit
GitHub: https://github.com/AbdulWahabWarind
YouTube: https://www.youtube.com/channel/UCBjgLqLK_2kU-3bwo4McrTw

Was this reply helpful? Yes No