13
There is 2 ways that timeentries record is created.
Data format of msdyn_date varies depending on the way.

1. from "import" button: "YYYY/MM/DD X:00:00"
*X is variable depending on users' timezone.

2. from "+New" button: "YYYY/MM/DD"

This difference causes big problems.

When time entries are exported to Excel, date of msdyn_date field changes in some cases

For example, if timeentries record (msdyn_date: 2021/08/20) created by User A (timezone: GMT+ 08:00) form "+New" button is exported to Excel by User B (timezone: GMT+ 00:00), msdyn_date is 2021/08/19 16:00:00 in Excel

Data format of msdyn_date should be "YYYY/MM/DD X:00:00" regardless of the way to be created
STATUS DETAILS
Declined
Ideas Administrator

This behaviour is due to the configuration of the field, currently the msdyn_date format is set to "Date only" which gives mm/dd/yyyy format, if we change the format to "Date and Time" then we can export the date with format mm/dd/yyyy h:mm but a new time field is getting added in the time entry form

As this is a breaking change for customers we will not be updating the form to include the time, but this is a simple mitigation for customers who need time.

Comments

R

The issue here is the timezone pushes the data te a day before, when you start working with dataintegration like PowerBI Azure Synapse link etc. the stored UTC gets delivered which also in our case is 1 or 2 hours back, so when storing yyyy/mm/dd+00.00.000 as local time, Dataverse stores this as yyyy/mm/dd(-1 day)+23.00.000

Category: Time Entries and Approvals