RE: Problem with date, comparison and calculated field
Hello Dima,
There are 3 different behavior which are associated with the date field.
User Local :
- This is the behavior of all date and time fields in the previous releases.
- The field values are displayed in the current user’s local time.
- In Web services (SDK), these values are returned using a common UTC time zone format.
Date Only :
- The concept of a time zone isn’t applicable to this behavior. The field values are displayed without the time zone conversion.
- The time portion of the value is always 12:00AM.
- The date portion of the value is stored and retrieved as specified in the UI and Web services (SDK).
Time-Zone Independent :
- The concept of a time zone isn’t applicable to this behavior. The field values are displayed without the time zone conversion.
- The date and time values are stored and retrieved as specified in the UI and Web services (SDK).
When the field behavior is User local then the UTC time(stored by CRM) will be converted to the User local time and date.
so depending on the user time zone it will be changed on the UI side.
When a date field is Time zone independent, it will be visible same to all the all users.
To implement your requirement you can make your field as the Time zone independent/Date only. Note : You can change from User Local to Time-Zone Independent any time, but can’t change from Time-Zone Independent to User Local once saved this way.
There are some limitations with respective to the date only field Please refer below article.
learn.microsoft.com/.../behavior-format-date-time-field
d365demystified.com/.../
Thank you,
Amit Katariya