Time Zone Changes Require Updates for Microsoft Dynamics CRM 3.0
Two Knowledge Base (KB) articles have been published that provide updated time zone definitions and a Wizard for adjusting dates and times in Microsoft Dynamics CRM 3.0 records that are affected by a change in time zone definitions. This is important for deployments that have users in the United States
Beginning in 2007, Daylight Saving Time (DST) will be extended in the United States. DST will start on March 11, 2007, which is three weeks earlier than usual, and it will end on November 4, 2007, which is one week later than usual. This results in a new DST period that is four weeks longer than in previous years.
How the DST Change Affects Microsoft Dynamics CRM
After the operating system has been updated with new time zone definitions, the updates and wizard synchronise Microsoft Dynamics CRM 3.0 time zone definitions with Microsoft Windows and adjust records associated with dates/times in Microsoft Dynamics CRM 3.0.
Most records in Microsoft Dynamics CRM 3.0, including custom records, include date/time stamps based on current DST rules. For example, activities that are scheduled during the delta period will appear one hour earlier than they should. Microsoft Dynamics CRM 3.0 calculates the Coordinated Universal Time (UTC) value when an activity is created. So if a user creates an appointment while Microsoft Dynamics CRM 3.0 is configured for the old DST rules and the appointment is scheduled during the new DST weeks, the appointment will appear one hour earlier than it should. The Microsoft Dynamics CRM 3.0 Update Time Zones Wizard helps adjust such records appropriately.
The Microsoft Dynamics CRM 3.0 updates and wizard are being released in advance of the United States Daylight Saving Time rules change in 2007, but they can also be used for general adjustments of calendar-related items based on changes in time zone definitions.