Answered

Date Only column is storing timestamp as well rather date alone

(0) Share

Report

Posted on by sthota

139

We have a Date Of Birth and other fields on PowerApps to be stored in Dataverse. We defined them as Date Only column datatypes and patching them as date only value onto Dataverse. However, it stores the timestamp as well internally on a random basis. We have to explicitly use DateTimeFormat() to display for the end user or while pulling into PowerAutomate flows.

Is there a way we can store only date alone in Dataverse?

Regards,
Srinivas

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (6)

Answers (1)

Sort by

Verified answer

Ram Prakash Duraisamy 5,877 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Open Model Driven apps --> click on gear icon at the top --> select advance Settings --> Navigate to Customisation --> Customize the System --> expand entities --> select the entity where the date is available --> expand the selected entities --> open the Date And time fields --> change the type of field from Date and Time to Date Only --> then Save the field and publish all Customisation.

Was this reply helpful? Yes No
Drew Poggemann 9,287 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @sthota ,

I struggle with this regularly. Behind the scenes in Microsoft it is really storing the time information with midnight on the Date Only fields. In Dataverse working with Model-Based apps it all works well but when working with Power Automate Flows, Canvas Power Apps, you need to be conscience of this. Recently I had a challenge that @ChrisPiasecki helped me with around this as well to store the date correctly in the Dataverse.
https://powerusers.microsoft.com/t5/Microsoft-Dataverse/Struggle-to-Set-Date-Only-Field-in-flow-for-Current-Date/m-p/1212518#M12975

From what I have found you just have to work with it correctly in flows etc. I wish it was simpler 😉

Hope this helps! Please accept if answers your question or Like if helps in any way.

Thanks,

Drew

Was this reply helpful? Yes No
sthota 139 on at

Like
a
(0)

Report
Copy link

Link copied!

@rampprakash Thanks for your detailed reply. We are using PowerApps Canvas Apps and we could achieve the same using the above steps mentioned. We had to change the Behavior settings of the column from User Local to Date only as below.

@dpoggemann Thanks for your reply. I have workarounds using DateTimeFormat() got it working fine without any issues on both PowerApps as well as in PowerAutomate flows. However, I wanted to know if there's a better way to make sure it doesn't save timestamp at all in Dataverse.

Was this reply helpful? Yes No
Drew Poggemann 9,287 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @sthota

no other option that I know of...

Thanks,

Drew

Was this reply helpful? Yes No
Drew Poggemann 9,287 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @sthota ,

In your original post I thought you had already chosen Date Only as the column type in Dataverse, sorry. It still has the issues I mentioned so you have to watch working with in flows, patching etc.

Thanks,

Drew

Was this reply helpful? Yes No
sthota 139 on at

Like
a
(0)

Report
Copy link

Link copied!

@dpoggemann You're right, I chose Date Only Field in Dataverse at the beginning itself, though it stores timestamp in that column unless we make the above settings changes on that particular in the Legacy Admin as mentioned by @rampprakash . Also, the conversions are taken care of in the flows with the older implementation and no change is required with the above changes also.

Was this reply helpful? Yes No