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?