Additional Migration Wizard Information

Owned by Becky Weinberg (Unlicensed)
Jul 20, 2021
2 min read

In the Step 2 of 4 dialog box in outbound migration, queries, parts, and dashboards are available in the upper-left panel. The following sections contain additional information about what they are and how Migration Wizard handles them.

Queries

These are the report queries that are configured in the Portal Query Explorer. Only the internal query type (Type = Internal) queries cannot be migrated by Migration Wizard.

All elements configured for a query in the Query Explorer are migrated. All the views created for a query are migrated. The default view if defined for a query is migrated. The criteria if defined in a query view are migrated.

Parts and Dashboards

Parts refer to dashboard parts that are built upon queries. Dashboards refer to dashboard views that are built using multiple dashboard parts.

The following configuration items in a dashboard part are migrated:

  • Part name

  • Category

  • Part type such as data, chart, or both

  • Selected fields and in the order as defined in the dashboard part

  • Column options such as group by, and calculation if any

  • Dates such as date rule as defined in the dashboard part

  • Results such as sort by, ascending or descending, show all results, or show first n results

  • Transform if used in dashboard part

All the dashboard parts contained in a dashboard view are migrated.

The location of the dashboard parts contained in a dashboard view are migrated and retained.

If the dashboard view uses a template that does not exist in a target environment, it is migrated.

The default view, if defined for a dashboard view, does not migrate since there is only one default view in the Dashboards window.

The criteria if defined in a dashboard view are migrated.

If a public dashboard view is selected in an outbound migration, the public dashboard view becomes a private dashboard view and the user who performed the inbound migration becomes the owner of it. It is then up to the user to re-publish the view as a public view and re-assign it to different users or business groups.