A workflow is triggered unexpectedly in Microsoft Dynamics CRM 4.0
This article has been archived. It is offered "as is" and will no longer be updated.
When you create a workflow that is triggered when a specific attribute is changed on an entity in Microsoft Dynamics CRM 4.0, the workflow is unexpectedly triggered when you make a change on an attribute that has a similar name.
This problem occurs because Microsoft Dynamics CRM evaluates attributes by using the Contains() method for the comparison between the values from the updated entity and the workflowdependencies object for the workflow.
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 updates
887283 Microsoft Business Solutions CRM software hotfix and update package naming standards
Article ID: 953099 - Last Review: 01/15/2015 02:16:49 - Revision: 4.0
Microsoft Dynamics CRM 4.0
- kbnosurvey kbarchive kbmbsworkflow kbautohotfix kbexpertiseinter kbfix kbmbsmigrate kbqfe kbhotfixserver KB953099