Reporting 2.0 - Custom Reports Migration Tool

The Import Custom Reports option on the Reporting 2.0 homepage lets you import all of your reports and folders from Custom Reports to Reporting 2.0, including multi-module reports. The process is quick and easy and is available from the Reporting 2.0 homepage.

Note: This option displays for users who have created at least one custom report and have permission to manage Reporting 2.0. It is important to note that it is possible for a user to migrate reports and not see them even though they were migrated successfully. This means the user does not have the permissions for the new report type. See Knowledge Central Related Articles.

To access Reporting 2.0, go to Reports > Reporting 2.0.

Migrate Custom Reports

To migrate a report or folder:

  1. Go to Reports > Reporting 2.0.
  2. Click Import Custom Reports. This opens the Import your Custom Reports slideout.
  3. Check the Convert Custom Report dashboard widgets to Reporting 2.0 dashboard widgets for selected reports option to convert dashboard widgets automatically from Custom Reports into Reporting 2.0 widgets. When the import executes, imported custom report widgets on existing dashboards automatically converted to Reporting 2.0 widgets without any further action needed for migration.
  4. Check the Enable delivery configurations in Reporting 2.0 for selected reports option to include the delivery schedule automatically for the imported report. If this option is not checked and the custom report has a delivery schedule, the schedule will need to be added manually once the report is imported.
  5. It is important to note that if the option is checked, then once the report is imported, the delivery schedule in the custom report becomes inactive. The delivery options are removed. However, the settings for scheduling are preserved in the custom report so that delivery options can be configured again.

  6. Select one or more folders/reports.
  7. Click Confirm. This adds your folders/reports to the Imported Custom Reports section on the Reporting 2.0 homepage. Note: The migration process may take a few minutes to finish. It may be necessary to refresh your browser page to view the migrated reports on the Reporting 2.0 homepage.

The folders and reports you migrate will also remain in Custom Reports and are available to continue using. Any changes you make in Custom Reports to a report that has been migrated are not reflected in Reporting 2.0 until you re-import the report into Reporting 2.0. Any changes you make to the migrated report in Reporting 2.0 are not reflected in Custom Reports.

The following rules apply to field prefixes:

  • For custom reports that were imported prior to the 16 August 2019 patch, the fields in the imported report do display section prefixes by default.
  • For custom reports that were imported after the 16 August 2019 patch, the fields in the imported report do not display section prefixes by default unless the report contains multiple fields with the same name (e.g., User First Name from User section and from Manager section).
  • If any report contains multiple fields with the same name, the Show Field Prefixes toggle is set to On, and this cannot be changed.

Edit Migrated Reports

To edit a custom report that you have migrated, click Edit from the Actions drop-down for the report. This opens the report in edit mode.

Delete Migrated Reports

To delete a custom report that you have migrated, click Delete from the Actions drop-down for the report.

Move Migrated Reports

When you migrate custom reports, the reports are automatically added to the Imported Custom Reports folder on the Reporting 2.0 homepage. You can move these reports to a different location in Reporting 2.0 to create the organization you prefer.

To move a migrated custom report:

  1. Click Move from the Actions drop-down for the report or folder. This opens the Move Report pop-up.
  2. Select the new location for the report.
  3. Click Move.

Considerations and Limitations

  • Re-Importing - If you select a folder or report that has already been imported, a Confirmation pop-up appears to let you know that the existing folder/reports will be overwritten with the current version from Custom Reports. You can choose to continue the import or cancel it.
  • Setting the Decimal Point - When creating a calculated field in Custom Reports, there is no option to set the decimal precision. Therefore, the calculated field is imported into Reporting 2.0 with the decimal precision set to "None." You can edit the imported calculated field into Reporting 2.0 and set the precision in Reporting 2.0 once the field has been imported.
  • Aggregation - Reporting 2.0 does not support aggregation on a calculated field that already contains an aggregation within the formula. If your custom report calculated field has double aggregation, the output between the Custom Report and migrated Reporting 2.0 report will differ.

Note: As part of the 17 July 2020 Patch Release, the following fields that were previously incompatible with the migration tool are now compatible and will not result in an error when migrating the custom report into Reporting 2.0:

  • Job Pool Succession Reports
    • All fields in the Incumbent section
    • All fields in the Successor section
  • Multi-Module Report Fields
    • # Parts User Attended
    • Exempted By(ID)
    • Exempted By(Name)
    • Transaction Remover
  • Succession Report Fields
    • All fields in the Incumbent section
    • All fields in the Successor section
  • Transcript/Training Report Field
    • Prerequisite Training Title

Custom Reports Usage Report

The Custom Reports Usage Report is only available to administrators and provides an export of custom report usage data in the portal. The Custom Reports Usage Report is accessible from the Reporting 2.0 migration tool.

Click Custom Reports Usage Report on the flyout to download a .csv file containing the Custom Report usage data for your portal. The report contains records for which the last run date was six months or less.

Administrators who are responsible for the migration of Custom Reports can use this report to pull Custom Report usage details directly from their portal to track the migration to Reporting 2.0 for their organization. Having a report on Custom Report usage gives administrators the information on which Custom Reports are still being run, how frequently and by whom. It can also provide insights into which Custom Reports to migrate into Reporting 2.0, based on the usage.

Frequently Asked Questions

Knowledge Central Related Articles