CRM has always had date fields which also store the time. The time is stored in the UTC time zone but displayed in the time zone of the user.
Even though it is possible to set a date field to show only the date, the time part can cause unexpected results. For example, consider a user in the GMT timezone who sets a date on record as 12th April at 0630 (in the morning). Even though the time control is not shown on the record form, the time is stored in the record as 0630. Now, if a user in the US on the West Coast looks at the record, the user's time zone setting in Personal Options will be applied to the date field. For the West Coast, the time zone is PDT which is 8 hours behind GMT. So 8 hours is subtracted from the date field and the date is shown to the US user as 11th April and not 12th April. Subtracting the 8 hours sets the time as 2230 (10.30pm) on the previous day.
Now in this release it is possible to set the behaviour of date fields and to truly ignore the time part.
The new options are defined in an option set called Behavior on the new field form for Date and Time.
|User Local||This is the existing behaviour where the time is adjusted according to the time zone of the user|
|Date Only||Values are displayed with no time zone conversion, the time is always 12.00AM but the time part of the control cannot be shown on the form (the only option for Format is Date Only)|
|Time-Zone Independent||Values are displayed with no time zone conversion, but the time can be shown on the form and is stored and displayed exactly as stored. The time zone of the user is not relevant.|