Article ID: 949569 - View products that this article applies to.
Consider the following scenario. In Microsoft Dynamics CRM 4.0, you enable the Duplicate Detection function. Then, you create a duplicate detection rule to detect duplicate records if records are updated. Next, you create a pre-update plug-in assembly for the update process. Finally, you update the records. The update process runs the assembly in a pre-update event.
In this scenario, the Duplicate Detection function cannot detect the duplicate records even if the duplicate records exist. When this problem occurs, the Duplicate Detection function still considers the original record values instead of the record values that are provided by the pre-update plug-in assembly.
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:
(http://support.microsoft.com/kb/949256/ )Microsoft Dynamics CRM 4.0 updates and hotfixes
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:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
(http://support.microsoft.com/kb/887283/ )Microsoft Business Solutions CRM software hotfix and update package naming standards
This hotfix will not address issues that involve lookups, pick lists, or owner fields. For these fields, this limitation is by design.