How to migrate reports into different directory with different package name

Check list of all posts

Overview

Migration of report doesn’t simply replicate folder structure from one version (e.g.10.1.1) to another version (10.2.1). The best way to handle this situation is to change folder structure in 10.1.1 to mirror new folder structure in 10.2.1, and make sure that all reports work, and then move all reports from 10.1.1 to 10.2.1, publish new packages in 10.2.1. If you have problem with production, then you can back deploy it to development server.

There are a few cases where we may encounter:

Case 1: Change data source, while query subject structure remains same.

Case 2: Move reports and packages to different folders

Case 3: Change package name

Case 1: Change data source, while query subject structure remains same

The idea is to change data source connection and keep query subject same as before. The advantage is that all related reports are not requested to change.

Normally, create new data source in new version 10.2.1. Then change 'Content Manager Data Source', and optional ‘Schema’.  The scheme change can be very useful to group all access user groups for that scheme, and make security much easier to manage.  One of problem in framework manager is to have multiple data sources pointing to same data source. The solution is to use XML edit to replace all data source names to a unique one and then delete duplicated source names

Case 2: Move reports and packages to different folders

Reports can be deployed to any folder, with simply copy and paste. However, the associated package path is saved in report specification. There are a few steps to move package from old folder to new folder:

1. Export reports only in deployment folder;
2. Import all reports in deployment folder;
3. Copy reports in right folder as specified;
4. Deploy new package into old folder, which can be found from old version. report should work at this stage;
5. Once confirmed that report has no problem, and then CUT package from old folder and PASTE to new folder. The package path reference on report specification will be changed accordingly.

Case 3: Change package name

1. Once confirmed that report has no problem to run, and then simply change package name in portal. In this case, the package name reference on report specification will be changed accordingly.
2. Change package name from framework manager, and republish it to override existing package.