cancel
Showing results for 
Search instead for 
Did you mean: 

Provice ability to turn UTC conversion off for a DateTime field

Author Name: Lu Azhari

We've seen with many clients the requirement to capture dates in an absolute value and not perform any of the CRM out of the box UTC conversion. An example for that is Date of Birth on Contact. This field has been configured as a Date Only field on the form, which stores the default time component of 12:00 AM. When someone in the east coast saves the Date of Birth as Oct. 30, 1982, it shows up to a user in the west coast as Oct. 29, 1982. This is annoying. I see how this makes sense when creating an Appointment or Task, but sometimes client require absolute dates that don't get converted to local time.

There are workarounds either at a client side level (JScript) or server level (plugins), but that is also very intensive when you have 10+ such date fields.

Can we have the ability to control UTC conversion at an attribute level? So when a DateTime field is added to an entity, the user can specify whether they want to turn off UTC for this field and in effect alwasy showing the same value regardless of the user's time zone?

Thanks.

Status: Completed

This feature is now available with release of date and time field behavior and format . Please refer :https://technet.microsoft.com/en-us/library/dn946904.aspx 

 

 Thanks,

 Srikumar Nair

 PM, Microsoft

Comments
D365Ideas_Admin
Regular Visitor
Status changed to: Completed

This feature is now available with release of date and time field behavior and format . Please refer :https://technet.microsoft.com/en-us/library/dn946904.aspx 

 

 Thanks,

 Srikumar Nair

 PM, Microsoft

D365Ideas_Admin
Regular Visitor
Yes! We need this and a true date-only field type (local date).
D365Ideas_Admin
Regular Visitor
Absolutely agree with this. I recently had to deliver a system that dealt with Flight Schedules. Pilots only deal with UTC times. Ground crew only deal in Local times. By that I mean local to the airport, not the CRM user. So for each flight event (Arrival, Departure, On Chocks, Off Chocks...) I needed 2 absolute, but different, datetime fields. I had to implement text fields with jQuery datetimepicker controls. A lot of work to overcome a simple problem.
n2
New Member
Yes please!! Birthdays and Anniversaries are other examples. They shouldn't change when users view the records in another time zone! We Desparately need a absolute (local) Date Field!
D365Ideas_Admin
Regular Visitor
A fat +1 from us. We need this!
D365Ideas_Admin
Regular Visitor
Thank you for your suggestion. We are considering this functionality for a future release of CRM. Mike Carter This posting is provided "as is" with no warranties, and confers no rights.
D365Ideas_Admin
Regular Visitor
Mike - Any chance of an update on where you are at with a fix for this issue please? Regards, Gareth
D365Ideas_Admin
Regular Visitor
This issue is marked as Resolved but I'm not aware of this feature being released or scheduled to be released yet. I would expect that 'Resolved' would indicate that this has been implemented already. Am I missing something here?
D365Ideas_Admin
Regular Visitor
This functionality needs to be included. The Date attribute should have an option to enable/disable UTC conversion. Much like number fields have min/max values, strings have max length or formatting, date should have UTC conversion opting. Having managed and architected CRM Dynamics projects the last 5 years for enterprise firms who have global offices, not having the ability to suppress UTC conversion creates a need on every project to write plugins which manipulate the time component on commit to the DB in order for a global community to all visualize the same date. How - by selecting a timezone which consistently displays the same date. Consider the following scenario in a capital markets firm: The customer has 9 global offices with 1200 users: NY, LA, UK, Tokyo, Sydney, Jakarta, Hong Kong, Paris, Singapore. An important characteristic for a client is the First Trade Date (common client attribute for wealth management firms). The offices routinely collaborate on services, marketing, and other operations. It is imperative that this date is viewed as the same date across all office. There are many approaches to handle this, and the most convenient to date on 4 different projects was to write a plugin to manipulate the time to a timezone which all offices view as the same day - this is not ideal. Another option is storing as a text, but then date conditions cannot be used by Advanced Find (among other lost functionality). As Microsoft CRM positions itself as a enterprise solution, this type of setting is necessary to support international operations. -Luke