You do not see the time zone information that should be created by a workflow rule that uses a date/time slug in Microsoft Dynamics CRM 3.0

Consider the following scenario:

• You log on to Microsoft Dynamics CRM 3.0 as a user in the (GMT-08:00) Pacific Time (US & Canada) time zone.
• You create a custom date/time attribute for the Account entity. The attribute is called customattribute. You add the attribute to the Account form.
• You create a workflow rule for the Account entity. The workflow rule uses a date/time slug for the custom date/time attribute. For example, you use a date/time slug for the customattribute field.
• You create an account that triggers the workflow rule.
• You log on to Microsoft Dynamics CRM as a user in the (GTM-07:00) Chihuahua, La Paz, Mazatlan time zone.
• To trigger the rule, you create another account.

In this scenario, you do not see the time zone information that should be created by the workflow rule when you create the second account. You do see the time zone information that was created by the workflow rule when you created the first account.

Note This problem occurs for new time zones. Additionally, this problem occurs for time zones that were changed after you applied the update that is described in Microsoft Knowledge Base article 925874. For more information about this update, click the following article number to view the article in the Microsoft Knowledge Base:

This problem was corrected in Microsoft Dynamics CRM 3.0 Update Rollup 3.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Microsoft Dynamics CRM 3.0 serverMicrosoft Dynamics CRM 3.0 client for Microsoft Office OutlookMicrosoft Dynamics CRM 3.0 client for Microsoft Office Outlook Compatibility Update

Installation information

Install this hotfix on computers that are running Microsoft Dynamics CRM 3.0 or that are running the Microsoft Dynamics CRM 3.0 client for Microsoft Office Outlook.

Prerequisites

No prerequisites are required.

Restart requirement

You do not have to restart the computer after you install this hotfix.

Removal information

To remove this hotfix from a computer that is running Microsoft Dynamics CRM 3.0, use Add or Remove Programs in Control Panel.

For more information about software update terminology, click the following article numbers to view the articles in the Microsoft Knowledge Base: