A workflow that is defined to be triggered on a "Record attribute change" condition may be unexpectedly triggered even though the monitored attribute is not changed in Microsoft Dynamics CRM 4.0
This article has been archived. It is offered "as is" and will no longer be updated.
A workflow is defined to be triggered on a "Record attribute change" condition in Microsoft Dynamics CRM 4.0. However, the workflow is unexpectedly triggered multiple times even though the value that the workflow monitors is not changed. Then, an infinite loop situation occurs, and the workflow fails.
Some entity attributes, such as the "Duration" attribute of the "Appointment" entity, may be unexpectedly updated by using the old value when you update other attributes of an entity instance of this kind. Therefore, customizations such as a workflow that monitors the "Duration" value change may be triggered unexpectedly.
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:
949256 Microsoft Dynamics CRM 4.0 updates and hotfixes
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updatesFor more information about Microsoft Business Solutions CRM software hotfix and update package terminology, click the following article number to view the article in the Microsoft Knowledge Base:
887283 Microsoft Business Solutions CRM software hotfix and update package naming standards
Article ID: 947762 - Last Review: 01/16/2015 02:46:43 - Revision: 3.0
Microsoft Dynamics CRM 4.0
- kbnosurvey kbarchive kbmbsworkflow kbexpertiseinter kbautohotfix kbfix kbsurveynew kbmbsmigrate kbqfe kbhotfixserver KB947762