Symptom
Optimized Design Experience story may show different behaviour in Edit and View mode under certain circumstances.
Issues may relate to scripting:
- In some cases a script function will not execute (such as Table_1.getNumberFormat().setScaleUnit(NumberFormatScaleUnit.Thousand))
- In other cases the script function will return incorrect or unexpected data.
Difference in behaviour may be seen as well in Thresholds or other story design features.
Environment
SAP Analytics Cloud, all versions up to 2025 QRC3 (2025.14)
Cause
- The code to display tables in SAC has been enhanced to support additional features and improve performance.
- A few regressive issues have been introduced due to this code change and need to be corrected.
Resolution
Our development team is investigating each reported issue and we are working on providing a fix in a future release
In the meanwhile it is possible to force the table to use the prior display code by implementing a feature that is not yet supported by the new code.
This will return the script code to the previous behaviour while we work on fixing the issue with the script functions.
Workaround steps
Option 1: Enable the "allow data point commenting) feature in the Builder panel for any table that is impacted by one of the identified script issues
Option 2: Add the following comment to the beginning of the "onInitialization" step in the script:
//Table_1.getPlanning();
If there are multiple tables you will need to add a comment referencing each table.
Keywords
KBA , LOD-ANA-UNS-SCR , Unified Story Scripting related Issues , LOD-ANA-AD , Analytics Designer , LOD-ANA-TAB , Table , Problem
SAP Knowledge Base Article - Public