- SAP Managed Tags:
To keep up with the SAP Analytics Cloud technology advancements, the classic stories on SAP Analytics Cloud need to be converted to the new Optimized Design Experience. Check out this detailed Blog on why you should move to the Optimized Experience.
Converting a classic story is easy: one can simply click on Convert to Optimized Design Experience. See image below.
As a next step of the conversion a popup will provide all further information if the story can be converted or not. In case of no blockers the story will automatically convert and be ready for further use.
However, in the case of blocker messages I have created this tip and tricks guide in form of a list which will be updated periodically with workarounds supported by step by step images of how to solve these blockers so that one can successfully convert a classic story to the new Optimized Experience.
Each blocker message title comes below with a suggested solution or a partial one.
1. Tables
Solution: OSE Tables have to be triggered manually as they do not convert automatically. After the table is selected you can click on the Designer/Builder and toggle Optimized Presentation ON. See image below.
After this step the blocker on conversion will disappear and you can convert the story.
2. Smart Insights
Partial Solution: For removing Smart Insights select the chart and double click on the smart insight text. After it is highlighted press backspace to delete it. See image below. As a last step save the story and the Smart Insights for that chart will be permanently removed. Now you can convert the story to OSE.
There are charts where the Smart Insights is not a visible text. To understand if a chart has Smart Insights on. The add button of that chart is grayed out like below. See image below.
In these cases create the chart from scratch without Smart Insights.
3. Geo widget - Point of Interest Layer
Solution: Switch the Geo map to another type of layer. E.g., from Point of Interest to a supported one like the Bubble Layer.
There is also the possibility to upload a shape for the layer. In this case, the recommendation is to use the Custom Choropleth Shape Hierarchies which is supported for SAP HANA and SAP BW.
4. Forecast
Solution: All time series with Forecast need to be switched off for the conversion to happen. To do that click on the chart, then it´s three dots pop up. Click on Add, Forecast, then toggle off the Automatic forecast. See image below. Once you have migrated to Optimized this type of chart you can add back the Timeseries forecasting feature as it is now supported in the 2024 Q3 QRC.
5. Group
The blocker message, Group, appears because there is a grouping between charts or text and icons.
Workaround: If you cannot recognize where the grouping in your story is, then you can also ignore this blocker message and proceed with the conversion. The story will be converted to OSE. However, always check that all charts are working and properly displayed after the conversion has happened.
6. Grid Pages
Grid pages can´t be converted, but they have to be created from scratch. Delete Grid pages before converting your story.
For information on how to create a table with a grid layout (on a responsive or canvas page), see Create and Use a Table with a Grid Layout.
7. Blended Table
Blended tables are also not supported for the moment (but will be added at a later time) when converting to Optimized Design Experience.
Workaround: From a Blended table, one can create two tables, showing the same information that was previously blended in one. These two new tables can be linked though a Linked Analysis. The Linked Analysis between them serves to get at the same time, similar information to the original Blended table.
e.g., Below, is a Blended table from two different models. One model brings in the PO Spend and the other brings in the Account Risk level for the Purchase Order Spent Analysis.
Workaround: Create two tables to cover the “Purchase Order - PO Spend” and “Purchase Order Spend Analysis by Risk level” as shown below.
Add the Linked Analysis between them, as it provides the ability to focus on the Risk level of a specific supplier. Showing at the same time its PO Spend and on the other table for the same supplier you can see the Risk Level. See image below.
Note: These workaround suggestions are based on my work with story conversion (SAC 2024.08). For SAP official product update of information on Optimized Story Experience restrictions see here.
2 Comments
