A bit type field is unexpectedly set back to the default value when you run a workflow rule to update some other fields of a record in Microsoft Dynamics CRM 4.0

When you try to assign default values to some bit-attribute fields in Microsoft Dynamics CRM 4.0 Workflow Designer, one or more of the following problems occurs:

• When you run a workflow rule to update some other fields of a record in Microsoft Dynamics CRM 4.0, a bit type field is unexpectedly set back to the default value.
• When you try to assign default values to bit-attribute fields in Microsoft Dynamics CRM 4.0 Workflow Designer, the default values are not assigned to some fields as expected.
  • If the bit-attribute field is in the List Box format, the value that is assigned to the field is Undefined or Null.
  • If the bit-attribute field is in the Check Box format, no value is assigned to the field.
  • You can assign the default value to a bit-attribute field only if the field is in the Radio Button format.

This problem occurs because the bit-attribute fields are reset when a workflow rule is triggered against a record that updates a field in another form. However, the Jscript code only assigns a default value to a field whose class name is Radio Button. Therefore, if the class name of the field is List Box or Check Box, the default value is not assigned to the field.

This problem is fixed in the latest cumulative update rollup for Microsoft Dynamics CRM 4.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about the terminology that is used to describe Microsoft software updates, click the following article numbers to view the articles in the Microsoft Knowledge Base: