Microsoft KB Archive/892515

= You cannot change a parent business unit in Microsoft CRM 1.2 =

Article ID: 892515

Article Last Modified on 8/11/2005

-

APPLIES TO


 * Microsoft CRM 1.2

-



SYMPTOMS
You cannot change a parent business unit in Microsoft Business Solutions CRM 1.2. Additionally, you may receive the following error:

The name for this record conflicts with an existing record name. You must use a unique name.

Note The error message is displayed only if the DevErrors=On setting exists in the Web.config file in the Microsoft CRM Web site directory. For more information about how to turn the DevErrors setting on, click the following article number to view the article in the Microsoft Knowledge Base:

857192 How to use the Web.config file to show more detailed error messages in Microsoft Business Solutions CRM (Microsoft CRM)



CAUSE
This problem occurs when you change a privilege for a default Microsoft CRM role in a child business unit so that the role has organization access. After this change, you cannot successfully create a new parent business unit for the child business unit.



RESOLUTION
To change a Microsoft CRM role so that the role has organization access, the privilege must be changed at the root business unit level. The changes made to the Microsoft CRM role at the root business unit level will propagate down to each child business unit role with the same name. You can then assign new parents or move the child business units in Microsoft CRM.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

This problem will be addressed in the next version of Microsoft CRM.



Steps to reproduce the problem
Assume that you have the following business unit structure:
 * Adventure Works Cycle
 * Region 1
 * Sales
 * Field Sales
 * Service
 * Field Service

In this scenario, Field Sales and Field Service business units exist at the same level. Field Sales has a parent business unit of Sales. Field Service has a parent business unit of Service. The Sales and Service business units exist at the same level. The Sales and Service business units have a parent business unit of Region 1.

To reproduce the problem in this scenario, follow these steps:
 * 1) Change the Account Create privilege in the default Microsoft CRM Salesperson role in the Sales business unit so that the role has Organization access.
 * 2) Save the Salesperson role.
 * 3) Try to change the parent business unit of the Sales business unit from Region 1 to Adventure Works Cycle.

You receive the error message that is mention in the &quot;Symptoms&quot; section. The Sales business unit will not receive a new parent.

Keywords: kbbug kbprb kbmbsmigrate kbmbsadministration KB892515

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.