Importing and exporting analytics

Overview

Importing and exporting analytics gives Data Hub users the ability to create a set of reports and package them so that they are reusable across multiple models. Stepping through the four steps of the import wizard, makes it easy to map to an existing or new cube, fix all resources and calculation references and finally validate the process for completion.

The import wizard

When importing analytics, you will need to re-map the analytics to a new cube server in the new environment. The import wizard provides a step by step process for mapping the connection details, resolving missing resources and members.

⚠ Important

The import wizard can be closed at any time and the remaining mappings completed later from the explorer right click menu.

Before mapping, it is important that the model's cube is processed. This enables the import wizard to find the new Cube and map all the reports and supporting resources to it.

  • Map to the Cube server, database and cube connection

In step one you map the imported analytics to any existing model's cube by specifying a cube server, and then choosing a database (warehouse) and cube of the model you want to map to.

¤ Note

If no suitable cube server exists in the current Data Hub installation, you have to create a new cube server before you can continue. Without correct permissions, you will not see the Create option.

  • Map missing supporting resources

On step 2 of the import wizard, the resources in the analytics needs to be mapped to the same resources in the existing model. Supporting resources like calculations are used in many of the reports and dashboards.

  • Map missing members

Missing members may be physical missing data members due to different source data in different models, e.g. years. If a particular report was using a particular year as a filter and the new model doesn't contain that year, it will present as a missing member.

  • Validate and resolve any remaining problems

Once all known resources and members have been mapped, run through the validate step to check that everything the analytics require to function has been mapped correctly.

Exporting analytics

Exporting Analytics groups resources (e.g. reports, dashboard, supporting resource) into a package that can be distributed and re-used.

  • A supporting resource is one on which another resource depends for its data or appearance. A dashboard has numerous supporting resources (e.g. analysis report and charts) that populate the individual cells of the dashboard.

  • A list of supporting resources is shown at the export stage. These can be included (by default) or omitted.

  • The supporting resource for any resource can be viewed by looking at the resource properties, Uses property.