Skip to main content

Celonis Product Documentation

Migrating Analysis to Views

Limited availability

This functionality is currently in limited availability. If you’re interested in trying it out, get in touch with us at Celopeers.

This migration guide discusses tools and gives tips to help you move dashboards built on Studio Analysis to Views. Celonis supports users in adopting our latest product development Views. We intend to invest all future innovation in these Views by reducing the effort to leverage existing dashboards built on Analysis.

Celonis will continue to maintain Analysis (by fixing bugs and ensuring that performance remains strong) but no further feature development will take place. For more information on Views and its capabilities, refer to the Studio feature availability matrix.

Checklist

Below is a checklist of the steps needed to migrate content from an existing Analysis to a Studio View.

Some of the steps are manual and some are semi-automated and supported with migration tooling. There are also features or components that cannot currently be migrated.

Important

Analysts will be able to access the toolkit and migrate any assets built on Analysis that they have permission to edit.

  1. Prepare by making sure there is a Knowledge Model and a View (new editing experience) present in the package to which you want to migrate.

  2. Check if the Analysis uses a load script. If it does, you’ll need to migrate manually.

  3. Export the saved formulas and any variables they use to Knowledge Models with the Export to Knowledge Model Tool.

  4. Check if the sheet you want to migrate uses a load script. If it does, you’ll need to migrate manually.

  5. Migrate one or more components with the copy-paste component tool.

  6. Leverage new capabilities to adjust the View and its layout to your needs before publishing. For more information, see Creating and configuring Views.

Detailed guide for Analysis to View migration

Make sure there is a Knowledge Model in the same package of the Studio Analysis where the saved formulas should be migrated to. If not, create a new Knowledge Model. Ensure the same Data Model is used in this Knowledge Model as the Studio Analysis.

Make sure that you have created a View where you plan to paste the components and that this View is using the same Knowledge Model that you export your Saved Formula to from Step 3.

Before proceeding with this step: Check if the Analysis from which you plan to start migrating components has an Analysis load script.

01-Migrating-Analysis-to-Studio_load-script.png

If it does not use a load script, proceed to Step 3.

If it does use a load script, choose which filter type you want to migrate it to.

Type

Description

Steps

Global Knowledge Model filter

By making a filter global it is going to be applied to all PQL statements in this Knowledge Model.

This is how the Analysis load script behaves. However, the difference is that the Knowledge Model is most likely used by several Views. Thus this setting makes sense if this filter should be applied to all PQL code of all Views using this Knowledge Model.

  1. Copy the load script filter statement.

  2. Open the Knowledge Mode and add a new filter.

  3. Enter a name for the statement.

  4. Copy and paste the filter statement.

  5. Toggle on the Global Filter setting.

Knowledge Model filter that is referenced by the View

You can reuse the filter statement in one View, or several as well as for individual component filters, but not all Views need to be filtered by it (compared with the global setting).

This makes sense if you have several Views in one Package that, before migration, were several Analyses with different load scripts. They still use the same data model and share metrics and attribute definitions and thus the same Knowledge Model.

  1. Copy and paste the load script filter statement.

  2. Go into edit mode of your View and click on the filter icon .

    02-Migrating-Analysis-to-Studio_create_a_custom_filter.png
  3. Create a custom filter (which you can save in the Knowledge Model).

Local View level filter

If there is no need to reuse this Filter for other Views or individual components you can also just save the filter statement locally in the View filter.

  1. Copy the load script filter statement.

  2. Go to edit your View.

  3. Click on the filter icon and choose "Custom filter".

  4. Paste the filter statement.

Before proceeding with this step: Go to your Analysis settings and saved formulas. Check whether your saved formulas are stored locally or in a Knowledge model.

For example, in the below screenshot most of the formulas are already in the Knowledge model, only one saved formula was stored locally on the Analysis. The export tooling will allow you to export this local saved formulas to the Knowledge Model.

KM_migration_example.png

If your saved formulas are already stored in a Knowledge model, proceed to Step 4.

If your have one or more saved formulas stored locally, export them to the Knowledge model that you want to use for the View.

Scope of the export saved formulas and variables tool

This tool allows users to export Saved formulas in Studio Analysis, and any formulas and variables used in those into the Knowledge Model KPIs in the same package. Therefore no permission management is required while exporting.

To export formulas to a Knowledge Model in another package ensure that the same data model used is available in the destination package. You can do this through Package Settings, see Variables. You can use the “Copy to” option to copy the Analysis to the destination package.

Important

Variables that are not used in a saved formula will not be migrated with this tool. This is to avoid cluttering the Knowledge Models with unused content. Most likely these variables are used directly in component configurations and will need to be migrated manually as part of the component migration. See 5. Copy and paste components from an Analysis into a View.

If your Analysis is connected to a Knowledge Model already, then saved formulas from the source “Knowledge Model” will not be selectable for export (to avoid duplication in the Knowledge Model).

Steps to export saved formulas to a knowledge model

This GIF shows steps 2 to 9 below.

03-Migrating-Analysis-to-Studio_exporting-saved-formulas-to-a-Knowledge-Model.gif
  1. Make sure there is a Knowledge Model in the same package of the Studio Analysis to be migrated.

    Learn more about what a Knowledge Model is and how it's used.

    1. Create a new Knowledge model if you do not yet have one by following the directions in Creating a Knowledge Model within an existing package.

    2. Ensure the same Data Model is used in this Knowledge Model as the Studio Analysis. A different Data Model being used will cause formulas to break.

  2. Go to Edit mode in the Studio Analysis you are exporting from.

  3. Click the hamburger menu in the upper left and select Saved formulas.

  4. Click Export to Knowledge Model to start the export.

  5. In the dropdown, choose the Knowledge Model to which you are exporting the formulas and their associated variables.

    Only Knowledge Models in the same package will appear in the dropdown.

    A warning message will appear if you select a Knowledge Model that does not share the same Data Model with your Studio Analysis, but you are able to proceed if necessary with the selected Knowledge Model.

  6. Select the formulas that you’d like to export:

    • Search by name through the search bar.

    • Select the formula you would like to include in the export by checking the checkbox next to the formula.

    • Or click the checkbox on the header row to include all selectable formulas in the export.

    Note

    Formulas that have the same name or the same PQL statement as an existing metric in the Knowledge Model will not be selectable. This is to avoid overwriting any existing formulas in the Knowledge Model.

    • Same name: Any component using the saved formula will automatically reference the Knowledge Model metric in the View and the reference will be automatically adjusted.

    • Same PQL with a different name: Components using the saved formula will need to be manually updated since the name of the saved formula in Analysis and the name of the metric in the Knowledge Model will differ.

    If you still want to export the saved formula, you will need to modify the formula either in Studio Analysis or in the Knowledge Model.

    Any variables nested within selected saved formulas will also be exported, and they are also included in this duplication check.

  7. Click Export to export the selected formulas.

    When the export is complete, you will see a success message.

  8. Close the window by clicking Done or go to the Knowledge Model by clicking Open Knowledge Model.

  9. Click Open Knowledge Model to validate the export. On the KPI page of the Knowledge Model, find the Saved formulas.

    Note

    You will not see any variables in the Knowledge Model immediately. You can find the variables directly in the PQL editor when using the Saved formula in a component in a View.

Before proceeding with this step: Check if the sheet from which you plan to start migrating components has a sheet load script.

  1. Click the settings icon.

    12-Migrating-Analysis-to-Studio_sheet-settings.png
  2. Select the Load Script tab.

    13-Migrating-Analysis-to-Studio_load-script.png

If it does not have a sheet load script, proceed to Step 5.

If it does have a sheet load load script, choose a filter type.

Type

Description

Steps

Knowledge Model filter referenced by the View tab

This is useful if you expect to reuse the filter statement for other Views, tabs, or components.

  1. Copy the Load script filter statement.

  2. Go into edit mode in your View and click on the filter icon at the View or tab level.

  3. Create a filter (which you can save in the Knowledge Model).

Local View level filter

Local View or tab-level filter

If you don't need to reuse this filter for other purposes, you can simply save the filter statement locally in the View or tab filter.

  1. Copy the Load script filter statement.

  2. Go to edit mode in your View and add a local filter at the tab or View level.

Scope of the tool

The Copy & Paste component tool allows you to export components built in Studio Analysis to a View. Component filters are automatically migrated with all mappable configurations. Some components or component settings are not yet covered.

The table below outlines the migration path for each component type. A prerequisite for migration is that the component exists in Views.

  • If the component is not available in Views, there will be no tooling.

  • If the component is available in Views, then either tooling already exists or the table indicates when tooling is planned. The table will also indicate If certain settings cannot be mapped.

Component

Current Migration Path

Limitations

Analysis - OLAP table

Supported by Tooling to Table

Color scheme is different between Analysis and Views:

  • Series color

  • Text color

“Calculate share in percentage” is not supported in Views.

Single KPI components

Supported by Tooling to KPI list (Gauge, Fill, Radial will also be migrated to KPI List (Number))

Formatting that is on longer supported in Views:

  • Background Color

  • Border

  • Title style

Configuration that cannot be mapped to Views:

  • Threshold for color

  • Name of the KPI formula

  • Name mapping

  • Position of subtitle

Dropdown

Supported by Tooling to Filter dropdown

Button

Supported by Tooling to Button

  • Open External Link to Go to the View or URL

  • Set Variable to Update variable

Only selected actions supported in Views.

Actions that are not available in Views:

  • Open Tab (coming)

  • Show Message

  • Delete selections

  • Load bookmark

  • Open Document

  • Launch Sheet Indexing

Visual styling options no longer supported:

  • Text color

  • Background color

  • Font choices

  • Component filter

Date picker

Supported by Tooling to Date Range.

Some options are mapped to other options or are not supported in Views:

  • Title is mapped to Label

  • Horizontal/ vertical alignment is not supported

  • Exclude component from user filtering is not supported

  • Component filter is not supported

Search

Not possible because of missing component in Views.

Component upcoming; tooling to be extended once available.

Button Dropdown

Currently manual to Input dropdown (Load entries).

Only setting variable supported (also only one, if you have a use case for setting more than one consider View variables of type object).

Analysis - Variable Input

Supported by Tooling to Input Box

Cropping

Not possible because of missing component in Views

Analysis - Text Component

Supported by Tooling to Toolbox

These coloring options are no longer supported in Views:

  • Text color

  • Background color

  • Text sizing setting in continuous size range

Image

Currently manual to image

Tooling upcoming.

Logo

Not possible because of missing component in Views

Component upcoming, tooling to be extended once available.

Line

Not possible because of missing component in Views

Component upcoming, tooling to be extended once available.

Process and Variant Explorer

Currently manual to Process Explorer and Variant Explorer

Tooling upcoming.

Column Chart

Supported by Tooling to Available chart types

Some options for alternative types to display KPIs are not supported in Views:

  • Views will show only one column and one line chart in combination

Color scheme is different between Analysis and Views.

"Calculate share in percentage" is not supported in Views.

Pie/Donut chart

Supported by Tooling to Pie/Donut chart

Color scheme is different between Analysis and Views.

“Calculate share in percentage” is not supported in Views.

Line Chart

Supported by Tooling to Line chart

Color scheme is different between Analysis and Views.

“Calculate share in percentage” is not supported in Views. 

Some formatting options are not supported:

  • Line thickness/style

  • Axis formatting

Area Chart

Component still missing - but alternative is to manually map to a Line Chart

Component upcoming, tooling to be extended once available.

Marker Chart

Component missing - but an alternative is to manually map to a line chart if the dimension is a time dimension, or to a bar chart if the dimension is categorical.

Component upcoming tooling to be extended once available.

Bubble Plot

Not possible because of missing component in Views

Component upcoming, tooling to be extended once available.

Histogram Chart

Supported by Tooling to Histogram

Color scheme is different between Analysis and Views.

“Calculate share in percentage” is not supported in Views. 

Explicit boundaries for the bars are not supported in Views.

Scatter Plot

Not possible because of missing component in Views

Component upmconing, tooling to be extended once available.

Pivot table

Not possible because of missing component in Views

Component upcoming, tooling to be extended once available.

Box Plot

Not possible because of missing component in Views

Component upcoming, tooling to be extended once available.

World Map

Not possible because of missing component in Views

Component upcoming, tooling to be extended once available.

Throughput Time Search

Not possible because of missing component in Views

Alternative: Histogram with Input dropdowns

Activity Explorer

Not possible because of missing component in Views

Alternative: Donut Chart with Input dropdowns

Steps to copy one or more components from Analysis and paste into a View
16-Migrating-Analysis-to-Studio_copy-paste-components.gif
  1. Make sure there is already a View where you intend to copy the component into. This View should also use the same Knowledge Model that you export your saved formula to, in order to avoid component breaking after export. Refer to Views for how to create a new View.

    To make it easier, you can open two different browser tabs in parallel - one tab with the Analysis you want to migrate and another with the new View.

  2. Switch to Edit mode in the Studio Analysis from which you are copying components.

    05-Migrating-Analysis-to-Studio_select-edit-mode.png
  3. To choose the components you want to copy, you can:

    • select individual components to copy them one-by-one;

    • select multiple components by clicking on the first component, holding down the CTRL key as you select additional components, and then pasting the selected components into your View all at once;

    • select all components in the Analysis by pressing CTRL + A so you can then paste them in to your View all at once;

  4. Right-click on any selected component and click Copy to View.

    17-Migrating-Analysis-to-Studio_copy-to-view.png

    You will see a notification on the right side of the screen that the components have been successfully copied.

    18-Migrating-Analysis-to-Studio_successful.png

    Note

    If a selected component cannot be copied, a yellow notification will display indicating which components could not be copied.

  5. Open the View you’d like to paste the component into and select Edit mode.

    To make it easier, you can open two different browser tabs in parallel: one tab with the Analysis you want to migrate, and another with the new View.

  6. Click Paste from Analysis on the right side panel under Smart Suggestions to paste the components or use the CTRL + V or CMD + V keyboard shortcuts.

    19-Migrating-Analysis-to-Studio_smart-suggestions.png
  7. Once the components are copied and pasted into your View, you can manually arrange the components to create the desired layout and edit the copied components directly in the View as needed.

Troubleshooting

Here are some tips on troubleshooting if components throw (expected) errors after pasting the component in Views that require manual fixes.

Error message or no data

You may see an error or no data is displayed. This is likely caused by a missing formula in the Knowledge Model.

20-Migrating-Analysis-to-Studio_create-missing-formula-1.png

You can click into the PQL editor for more information and resolve the issue by creating the missing formula or parts of the formula in the Knowledge Model used in this View.

21-Migrating-Analysis-to-Studio_create-missing-formula-2.png
Column names do not appear as expected

You may see column names that do not appear as you expect, which is not unusual for columns where only the default name is used.

22-Migrating-Analysis-to-Studio_adjusting-column-names-1.png

To make the names more readable, you can edit them in the “Columns” section of the Settings panel.

23-Migrating-Analysis-to-Studio_adjusting-column-names-2.png
24-Migrating-Analysis-to-Studio_adjusting-column-names-3.png
Dropdown dimension shows “Data Source not found”

In the Filter dropdown section, you might see the dropdown dimension showing “Data Source not found” while the dropdown is displayed. This happens when the default column name is used for the column that was used to create the dropdown.

25-Migrating-Analysis-to-Studio_data-src-not-found-1.png

To fix this (which is not essential), you can either go to edit and exit to allow Views to pick up the default name, or edit to give it a new name.

26-Migrating-Analysis-to-Studio_data-src-not-found-2.png

Views come with a set of entirely new capabilities that you might want to leverage when migrating your existing Analyses. In this case, it makes sense to consider those early on during the migration.

An example is the built-in filter bar.

In Analysis, many customers tried to group filter components on one side of the sheet and visually differentiate them from the rest of the content.

14-Migrating-Analysis-to-Studio_analysis-grooup-filter-components.png

Views offer a built-in filter bar that can be collapsed and expanded on demand.

Tip

Copy your filters into the new built-in filter bar to leave more space on the main View for visualizing your data.

15-Migrating-Analysis-to-Studio_views-offer-a-built-in-filter-bar_.gif

Other new capabilities in Views include:

Version history

Version 1.0: September 2024

Version 2.0: October 4, 2024 - Added multi-select for copying and pasting components.