SAP Knowledge Base Article - Public

3631371 - Incorrect Story Version status in when using model SAC_PERFORMANCE_E2E After conversion to Optimized Mode in SAP Analytics Cloud

Symptom

  • Incorrect Story Version status in when using model SAC_PERFORMANCE_E2E After conversion to Optimized Mode in SAP Analytics Cloud
  • It is observed that, for a converted Optimized Design Experience story, this Story Version may still return value like Classic, which is not expected.

Environment

SAP Analytics Cloud 2025.8

Reproducing the Issue

  1. Create a story in Classic Design Experience mode.
  2. Open and perform some action, then convert it into Optimized Design Experience mode.
  3. Create a new story based on SAC_PERFORMANCE_E2E model.
  4. Create a table and add Story, Story Version into the table.
  5. Add filter to only filter the story created in the 1-2 steps.
  6. Find that, for the same story, Story Version has multiple value like Classic, Unified Story.

Cause

  • This behavior is by design.
  • The backend data in SAC_PERFORMANCE_E2E recorded the status when every operation happened. In this case, because the story was originally a classic one, and then converted into optimized. So for the same story, it has two different version states during all time.

Resolution

If user only wants to check the latest data, in the same table, user can use another field Action Start Time to filter the time after the conversion time. 

See Also

Your feedback is important to help us improve our knowledge base.

Keywords

sac_performance_e2e, optimized mode, classic mode, story metadata, inconsistent values, sap analytics cloud, data visualization, story, action start time, filter, backend data, version states , KBA , LOD-ANA-DES , Story Design & Visualizations , LOD-ANA-XUS , Performance and usage statistics and tooling in SAC , Problem

Product

SAP Analytics Cloud 1.0