1756813 - Error:"The name "<Repository Object>" is not unique. It has been used by peer objects, or it has been used by the same type object in the datafoundation, or business element." when doing XML import in Business View Manager

• Unable to overwrite the existing LOVs using XML import even if "Overwrite CUID if exists" is checked in Business View Manager.
• Error:"The name "<Repository Object>" is not unique. It has been used by peer objects, or it has been used by the same type object in the datafoundation, or business element." when doing XML import in Business View Manager 

• Crystal Reports 2008
• Business Objects Enterprise XI 3.1

1. Create a sample report (REPORT.rpt) with dynamic parameter "MYPARAM" in CR designer and save it locally.
2. After saving it locally, publish it to Business Objects Enterprise so that it creates the Dynamic LOV (say LOV1) and other Repository objects in "Dynamic Cascading Prompts" folder.
3. Log on to Business View Manager and click browse to Tools--> Export to open "Export" window.
4. Export LOV1 to XML file (test.xml) and make sure you uncheck "Preserve folder Structure" check box while exporting.
5. Delete Data connection created for the LOV (so that it removes all the dependent objects including LOV).
6. Re-save the local Crystal Report (REPORT.rpt) created in step 1 to Repository (so that it creates all the repository objects again with same name but different CUID in the folder "Dynamic Cascading prompts" ).
7. Now we have the objects that were deleted in step 5 but with different CUID
8. Import the XML created in step 4 (test.xml) to "Dynamic Cascading Prompts" folder.
9. Error:"The name "<Repository Object>" is not unique. It has been used by peer objects, or it has been used by the same type object in the data foundation, or business element." will popup

Error occurs when trying to XML import Repository Objects to a folder in destination Repository which already has same type of Object with same name but with different CUID. Previous Improper migrations might be the cause of this issue

This issue arises if the CUIDs of Repository objects is not maintained throughout the Life Cycle Management. If the Integrity of CUID is maintained then while doing XML Import of Business Views, checking "Overwrite if CUID exists" check box successfully imports the updated Repository Object, which are usually only edited in Development Environment.

Integrity of CUIDs of Repository Objects should be maintained throughout Life Cycle Management. If broken then delete the problematic Repository Objects and re-import the objects with correct CUIDs.

WORKAROUND:

1) Rename source objects before generating XML or rename destination objects before importing XML

                          OR

2) Create a new folder in destination Repository, and choose this folder while importing the Objects from XML

KBA , BI-RA-CR , Crystal Reports designer or Business View Manager , BI-BIP-DEP , Webapp Deployment, Networking, Vulnerabilities, Webservices , Problem