Some child records and related records are unexpectedly visible to the previous record owner after you reassign records to another record owner in Microsoft Dynamics CRM 4.0

When you reassign records to another user in Microsoft Dynamics CRM 4.0, some child records and related records are still visible to the previous record owner. However, you expect that the child records and related records are no longer visible to the previous owner because of the security role settings and the cascade operation settings.

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:

After you apply the hotfix, you must complete one of the following methods to fix existing data records.

Method 1 - Tool:

Locate the Microsoft.Crm.SE.FixPOAForCascadeAssign tool in the C:\Program Files\Microsoft Dynamics CRM\Tools directory.
To run the tool, follow these steps:

1. Click Start, click Run, type cmd, and then click OK.
2. Change directories to the C:\Program Files\Microsoft Dynamics CRM\Tools directory. For example, type cd C:\Program Files\Microsoft Dynamics CRM\Tools\
3. Type Microsoft.Crm.SE.FixPOAForCascadeAssign.exe <OrgName>, and then press ENTER.
   
   Note The placeholder <OrgName> is a placeholder for the actual name of your organization.

If you want to run the tool specifically for one ObjectId, type the following: Microsoft.Crm.SE.FixPOAForCascadeAssign.exe <OrgName> <ObjectId> <ObjectTypeCode>

Note The placeholder<OrgName> is a placeholder for the actual name of your organization, <ObjectId> is a placeholder for the actual object that you want to fix, and <ObjectTypeCode> is a placeholder for the type of the object. For example, type Microsoft.Crm.SE.FixPOAForCascadeAssign.exe AdventureWorksCycle 21315527-0C71-DB11-8F1D-0017A41F0DE7 1.


Method 2- Manual:

1. Change the cascade operation settings for any relationship for any entity in Microsoft Dynamics CRM.
2. Save the changes, and then publish the customizations.
3. If you do not want to keep the changes that you made, revert your changes, and then repeat step 2.
4. Reassign the parent record to the new user again. You expect the child records and related records are visible to the new record owner and invisible to the previous record owner.