User Community Service Desk Downloads
If you can't find the product or version you're looking for, visit

Data Stories 14.5.0 Upgrade Notes

This article outlines the transition process for legacy reports, widgets, and features as Data Stories is upgraded to version 14.5.0.

The upgrade procedure is automated and no user action is needed.


Previously, three report types were available in Data Stories. Each of them has a unique migration process.


Stories are migrated as follows:

  • Creating a new story: A new Story report is generated, maintaining the original ID and name.

  • Visualization collection: All widgets embedded in the story are migrated to visualizations within a new collection, named after the original story.

  • Layout transformation: The original layout is transformed as follows:

    • The animated section, which contains multiple steps, is split into individual sections for each step.

    • The stacked section is directly converted into a new section while keeping the original grid layout. Any hidden widgets on the slide (for instance, eight steps in a 4x4 layout) are individually recreated as full-screen sections.

    • Insights are not included in the migration process.

  • Explainer transition: Each explainer is associated with a parent widget if possible.

    • Parent Widget: Typically, this is the preceding widget or step, as identified from the widget sequence. It must contain data and cannot consist of text paragraphs, headings, hero images, YouTube media, or another explainer.

    • If a parent widget isn’t found, the explainer is converted into a static content text widget, with information shown in plaintext and disconnected from the original data.

    • Otherwise, the explainer is converted into the parent widget description. All the information defined in the widget configuration is preserved in plaintext, even if it is disconnected from the original data source.

  • Visualization migration: Visualizations are migrated fully in their original form, except for those that have been discontinued.

    • For instance, the Text formula widget is transformed into a KPI widget while the multiseries formula widget is migrated as it is but is currently not supported in the UI.

    • Some visualizations are converted to static content for compatibility reasons (such as text, headings and explainers, hero images, YouTube videos).


Dashboard reports go through the following process:

  • Creating a new dashboard: A new Dashboard report is created, preserving the original ID and name.

  • Visualization collection: All widgets in the dashboard are migrated to a new visualization collection named after the dashboard.

  • Layout transformation: The layout, originally a freeform canvas allowing overlapping widgets, is transformed into a grid layout using a best-effort algorithm. Widgets that cannot fit into the grid due to overlap are adjusted to fit into the next available row.


Data Exploration reports are transformed as follows:

  • Creating a visualization collection: No new report is created. Instead, the exploration is converted into a new visualization collection.

  • Custom metrics preservation: Custom metrics are preserved and can be located within the visualization.

  • Sharing records: Note that these are not migrated.

Global filters

After you open a story or a dashboard, global filters should be migrated to the UI.


Old story and dashboard thumbnails are migrated but might not keep the same layout after migration. After you open a report or a visualization, new thumbnails are updated or generated for dashboards, story sections, and visualizations.

Potential issues

If migration fails for a story or its components (sections or widgets), they are skipped.

This does not interrupt the overall migration process. Instead, a warning is logged by the migration script.

Known limitations

  • When using filters on columns designated to represent IDs (for example, Monitoring Project ID, Dimension ID, Processing ID, Catalog Item ID), users must provide the complete ID string for the filter to function correctly. Partial string searches give no results and might lead to errors.

  • The Search in all column values feature is currently turned off if you attempt to use it with any columns designated as ID columns.

Was this page useful?