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.
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.
Check if the Analysis uses a load script. If it does, you’ll need to migrate manually.
Export the saved formulas and any variables they use to Knowledge Models with the Export to Knowledge Model Tool.
Check if the sheet you want to migrate uses a load script. If it does, you’ll need to migrate manually.
Migrate one or more components with the copy-paste component tool.
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.
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. |
|
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. |
|
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. |
|
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.
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.
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.
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.
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.
Go to Edit mode in the Studio Analysis you are exporting from.
Click the hamburger menu in the upper left and select Saved formulas.
Click Export to Knowledge Model to start the export.
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.
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.
Click Export to export the selected formulas.
When the export is complete, you will see a success message.
Close the window by clicking Done or go to the Knowledge Model by clicking Open Knowledge Model.
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.
Click the settings icon.
Select the Load Script tab.
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. |
|
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. |
|
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 |
|---|---|---|
Supported by Tooling to Table | Color scheme is different between Analysis and Views:
“Calculate share in percentage” is not supported in Views. | |
Supported by Tooling to KPI card (Gauge, Fill, Radial will also be migrated to KPI card (Number)) | Formatting that is on longer supported in Views:
Configuration that cannot be mapped to Views:
| |
Dropdown | Supported by Tooling to Filter dropdown | |
Supported by Tooling to Button
| Only selected actions supported in Views. Actions that are not available in Views:
Visual styling options no longer supported:
| |
Date picker | Supported by Tooling to Date Range. | Some options are mapped to other options or are not supported in Views:
|
Search | Currently manual to Search. The following mappings are supported (Analysis to Views):
| Not currently supported in Views:
|
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). | |
Supported by Tooling to Input Box | ||
Cropping | Not possible because of missing component in Views | |
Supported by Tooling to Toolbox | These coloring options are no longer supported in Views:
| |
Currently manual to image The following mappings are supported (Analysis to Views):
| Not currently supported in Views:
| |
Not possible because of missing component in Views | Component upcoming, tooling to be extended once available. | |
Not possible because of missing component in Views | Component upcoming, tooling to be extended once available. | |
Currently manual to Process Explorer and Variant Explorer | Tooling upcoming. | |
Supported by Tooling to Available chart types | Some options for alternative types to display KPIs are not supported in Views:
Color scheme is different between Analysis and Views. "Calculate share in percentage" is not supported in Views. | |
Supported by Tooling to Pie/Donut chart | Color scheme is different between Analysis and Views. “Calculate share in percentage” is not supported in Views. | |
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:
| |
Component still missing - but alternative is to manually map to a Line Chart | Component upcoming, tooling to be extended once available. | |
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. |
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. |
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
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.
Switch to Edit mode in the Studio Analysis from which you are copying components.
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;
Right-click on any selected component and click Copy to View.
You will see a notification on the right side of the screen that the components have been successfully copied.
Note
If a selected component cannot be copied, a yellow notification will display indicating which components could not be copied.
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.
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.
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.
 |
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.
 |
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.
To make the names more readable, you can edit them in the “Columns” section of the Settings panel.
 |
 |
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.
 |
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.
 |
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.
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.
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.