Migrator for Notes to SharePoint 6.15 - User Guide

Reports

All reports are found under the Reports node. Each report is represented by a tree node. A number of standard reports are provided that summarize or detail the data collected by the user. The standard reports are found directly under the Reports node. They cannot be edited or customized within the console.

NOTE: The current version of Migrator for Notes to SharePoint includes only a limited set of standard reports and charts. Additional reports may be downloaded separately from the Quest support web site and from http://notes2sharepoint.org.

Microsoft Report Viewer 2012 is used by the console for viewing all reports. If this component is not installed, the reporting functionality will be not enabled. Report Viewer 2012 may be downloaded from the following location: http://www.microsoft.com/en-us/download/confirmation.aspx?id=35747.

To view a report, select the corresponding report node. The resulting report can be viewed in the Results View. From the Results View, you can navigate through the pages of the report, print the report or export the report using the report toolbar on the top of the Results View.

Figure 6. Detailed database report

For more information on the Report Viewer capabilities, go to http://msdn.microsoft.com/en-us/library/ms251671(VS.100).aspx.

Standard and advanced reports

The installation adds several report XML and RDLC files in the Standard Reports folder. Reports shipped with the console are listed as children of the Reports node and cannot be edited or customized within the console.

Each report consists of:

The following is a list of Standard Reports:

The following is a list of Advanced Reports:

Report dataset supports the following tables:

The RDLC report files contain the dataset schema needed to design reports. There is no external XSD schema file provided containing this information. When using the Create New Custom Report feature described below, a starter RDLC is created containing the dataset schema ready for designing the report in a suitable 3rd party tool such as Visual Studio Professional.

Custom reports

In addition to the standard reports that are provided, users can design their own.

All custom reports appear under the Custom Reports scope node under the Reports node. The Custom Reports node has actions to add, edit or delete Reports.

The Copy Report function performs the following actions:

Other view properties such as column selection, column ordering and sorting are defined using the View menu item of the Actions pane. Select the submenu item Add/Remove Columns to change the report’s column selection as well as to reorder the columns. The Sort By menu items allow you to change the field that the report is sorted on.

Another way to add a new custom report to the Console is to simply add the report’s RDLC and XML files to the Custom Reports folder. The next time the Console restarts or refreshes, the new report nodes will appear under the Custom Reports node.

To share a report, you can copy the .XML and .RDLC files from your Custom Reports folder to another user’s Custom Reports folder.

With new releases of the Migrator for Notes to SharePoint Console, additional reporting fields and tables may be provided, or existing ones renamed. Older custom reports may need to be updated in order to be compatible with the newer dataset schema.

To support this, the Update Report Definition action is available when a custom report is selected. This action will create a time-stamped backup of the current report RDLC file prior to performing the required upgrade of the report’s dataset definitions. Once the report is updated, new tables and data columns are available for customizing the report.

The Update Report Definition action is only available for reports within the Custom Reports folder and is usually only necessary in the following cases:

Task history

All long running tasks are managed using a common task management facility found in the Task History node. When a process is run in the Console, Task Records are created and either dispatched to worker threads that perform the actual work or added to a task management queue, in which case they are performed serially in a predetermined order.

When the Task History node is selected, the Results View of the console shows a list of all tasks (pending + running + recently completed). This view is automatically updated in real time.

The view displays the following information for each task listed:

Each task record and its details are viewable in the task property sheet. If a running task is being viewed in a property sheet, the information on the property sheet updates as the task status changes.

Certain tasks such as migration jobs, will generate a log file. The log files are saved as part of the Task Record in the Repository. When a log file becomes available, additional tabs are displayed in the task property sheet. These tabs are the summary and detailed versions of the log file similar to the Migrator for Notes to SharePoint Designer log viewer. For more information, see Migration job logging. Log files can be exported to the file system by selecting the Export Log task action once the task is selected in the results view. To migrate the failed items for a task, right click on the task, and click Migrate Failed Items. For more information, see Migrating failed items.

Additionally, the Task Records that relate to a particular database should be displayed in that database's Migration History tab of the database property sheet.

Any tasks that are tied together to run sequentially, like running multiple migration jobs for a single database, are displayed as separate tasks with a wrapper task, for example "Content Migration Sequence".

One or more tasks can be purged from the Repository by selecting the tasks in the results view and the selecting the Delete action from the Action view.