Skip to Content

How to migrate Business Views from one environment to another (Specific to XI 3.1)?

When you create a dynamic parameter in your report and save it to the BusinessObjects Enterprise, a Business View structure is created within the repository. This structure includes the below components:

1. Data Connection

2. Data Foundation

3. Business Element

4. Business View

5. List of Values

6. List of Values – Prompt Group

If you open a report from BusinessObjects Enterprise and edit a dynamic parameter then you will find that it refers to a List of Values – Prompt Group. You have to migrate these Business View Manager Components to each such environment where your reports are migrated (which refers these BusinessObjects components). If you do not do so then, when refreshed in infoview/CMC, the report’s parameter page will not show the drop downs for the dynamic parameters.

The procedure below explains how you can migrate the Business View Manager components from one environment to another:

1. Login to the Business View Manager on your local system.

2. Go to Tools->Export.

3. Click on the Choose “XML button”. A “Save As” dialog box will open. Choose the location and name of the XML File (If the file does not exist then create an empty file with “.xml” extension).

4. Navigate the Business View and the List of Values you need to migrate. Note that You will only see the Business View and the List of Values components in the “Export” dialog box. All other referenced components, referenced by LOV and Business VIew ex. Data Connection/Data Foundation/Business Element, List of Values – Prompt Group(s), will be migrated with them.

5. Use the arrow keys (> and <) keys to add and remove the Business Views and LOVs to the “Selected Business Views” list-box.

6. Un-chek the check-box “Export Security Information”. As the security Structure might be different in different environments, we have chosen to un-check this option.

7. Check the check-box “Preserve folder structure”. This will create the folder structure as per source, if not exist, in the target environment.

8. Hit Ok.

The steps mentioned above exports the selected Business View components and their dependent/referenced components to the XML file on the selected location in Step 3.

Steps below mentions how to import the Business View components to the target environment.

1. Login to the Business View Manager on your local system.

2. Go to Tools-> Import.

3. Click on the Choose “XML button”. An “Open” dialog box will open. Choose the location and name of the XML File.

4. Choose the XML file saved in “Export” steps.

5. Choose the Root node (which shows the Central Management Console name) under the category “Select the import folder”. If you choose any other node then the folder structure of the source system will be created under that selected node on target.

6. Check the check-box “Preserve CUID when importing objects”. This will make sure that new CUID are not created for the objects we are importing in target.

7. Un-check the check-box “Overwrite CUID exists”.

8. Un-check the check-box “Merge folder scurity”.

9. Hit Ok.

And that’s it! These steps should migrate the Business View Components to the target from source.

You must be Logged on to comment or reply to a post.
      • After following these steps, migrating some reports, updating the Data Foundation table location, and updating the data source in the data source expert, I get an error when previewing my reports in CR 2008. Can not open database, unknown database connector error. I am assuming it can’t find the connection string, but I am not sure why.

        • Hi John

          You can look into the below areas:

          1. If your connection is an ODBC connection then check if it is created on the server where your BusinessObjects is installed (where you migrated the Business View Manager components). If the connection is an OLDB connection then try to use some other method to connect the database (may be an UDL file connection).

          2 Check if the password is correctly set in the data connection.

          3. Check if you can query the Business View directly instead of using the List of Values directly in the parameter.

          The steps above are just to identify the location where exactly the problem is.