When I select March 14, 2021 in a date field it defaults back to March 13, 2021 instead, why?

(0) Share

Report

Posted on by USA80

Hello,

I have a date field called, "Effective Date" and when I select the date of 3/14/2021, and then click off the field, it automatically changes the date to 3/13/2021. When I go back and select 3/14/2021 and tab off the field again, it stays. What would cause it to go to 3/13/2021? I do not have a business rule and don't see any workflows that is causing this to happen. This is on the Opportunity record. The "Effective Date" field is setup as:

Data Type = Date and Time

Field Type = Simple

Behavior = User Local

Format = Date Only

IME Mode = auto

It only happens for this date that I can tell and it happens to multiple users. Any ideas on how to fix this? Please let me know, thank you.

I have the same question (0)

All responses (2)

Answers (2)

Verified answer

Arun Vinoth 11,615 Moderator on at

Like (0)

Report

I will investigate in this direction, is there any Javascript or plugin/action code doing date manipulation. Although you mentioned about Business rule and workflow, double check the logic everywhere & verify with other team members.

Another possibility is - timezone. If the record is created/updated by an user in US timezone will have previous date, but the same record field will show next day for Australia users. It is expected bcoz of User local setting and that too for a date only field.

Change it to timezone independent in lower environment and test it to verify this issue is fixed. Then do it in production.

Was this reply helpful? Yes No
Verified answer

Wahaj Rashid 11,321 on at

Like (0)

Report

Hi,

Thank you for your query.

When the Behavior is "User Local", date is stored with the User 's Local time (this means the time information is taken from client machine). This is possible, in edge cases, due to time information (which is in UTC), date value can take you a day back (based on time information stored along with Date).

Please note, Format property controls how you want to display the value, when set to Date Only, it doesn't mean time part is ignored. Time part is still stored along with Date.

To fix this, you can change the Behavior to Date Only, this way the ate value will be stored with default time (12:00 AM) and date will not be changed (you can think of this Date Only field).

You can read more about Date Behaviors here:

https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/behavior-format-date-time-attribute#specify-the-behavior-of-a-date-and-time-attribute

Was this reply helpful? Yes No