SAC 2026.20: story object size and a performance check on save
New in SAP Analytics Cloud 2026.20: see how much each object adds to a story and get a warning on save when performance recommendations are still open.

Table of contents
Most of us have inherited an SAP Analytics Cloud story that takes forever to open and that nobody dares to touch. Release 2026.20 adds two helpers to the story designer: an analysis of the size of every object in a story, and a warning on save when performance recommendations have not been applied. They are not flashy features, but they target a problem I see in almost every tenant.
What is new and what state it is in
SAP announced both features on 16 November 2026 in two SAP Community articles that place them in release 2026.20. According to the What’s New – 2026 Releases page in the SAC help, quarterly release QRC4 2026 bundles versions 2026.16 to 2026.21, so tenants on the quarterly cycle get them with QRC4 2026. These are not beta or roadmap items: they are part of the release.
| Feature | Where you find it | What it solves |
|---|---|---|
| Size analysis (Story Object Size) | Story Object Size tab in the Info Panel, in edit mode | Knowing which pages and widgets make the story heavy |
| Performance warning on save | When you choose Save, Save As… or Save a New Version… | Making sure nobody saves without seeing the recommendations |
Story Object Size: where the weight of a story sits
SAP’s article starts from a familiar situation: SAC enforces a size limit on stories and blocks the save when you exceed it, but it does not tell you which object is to blame. The new tab fills that gap.
According to the help, with the story in edit mode there are two ways to run it:
- Open the Info Panel, go to the Story Object Size tab and choose Analyze (or Analyze again if you have run it before).
- In advanced mode, go to Tools → Performance Optimization → Analyze Object Size.
The result shows the total story size against the allowed limit and splits it into two blocks:
- Widgets: pages and their widgets, each with size in MB, share of the total and type.
- Others: everything that is not a widget, such as variables, global scripts, theme definitions, configuration flags and other story metadata.
You can view the list as a tree (the default, with expandable pages) or as a flat list, and sort it by size. The Action column takes you straight to the object on the canvas with its builder panel open.
There is one important nuance the help makes clear: the size is that of the serialized story definition (structure, widgets, scripts, layout and so on). It does not include model data. So this tab will not explain a slow query; that is still the job of Performance Insights and the performance recommendations. The help also notes that in stories with few widgets the Others block takes a larger share, so a high percentage there is not always a bad sign.
The performance warning on save
The Performance Recommendations tab in the Info Panel has been available in the optimized story experience since Q3 2025. The problem, as SAP explains, is that many designers never looked at it: SAP’s telemetry shows that a significant share of stories carry recommendations that were never acted on.
From 2026.20, if a story has at least one known performance issue and you choose Save, Save As… or Save a New Version…, SAC shows a dialog with three options, according to SAP’s article:
| Option | What it does |
|---|---|
| Save | Saves the story with its known issues and records the event in the Activity Log |
| View Recommendations | Cancels the save and opens the recommendations panel, grouped by impact level |
| Cancel | Cancels the save and returns you to the story as it was |
The dialog also has a Don’t show this message again checkbox for those who prefer not to see it.
For a BI team, the interesting part is the Activity Log entry: for the first time you can find out which stories were saved with known performance issues, without waiting for users to complain.
How I would use it in a BI team
This is my own view, not SAP documentation:
- Before transporting or publishing, have the designer run the size analysis and check the recommendations. I would add it to the story review checklist, just like naming or filters.
- Start with legacy stories. In stories that have evolved for years, the Others block (variables and scripts nobody uses anymore) tends to grow unnoticed.
- Combine it with page weight. SAC’s best-practice guide gives each widget a weight and sets an ideal maximum of 5 units per page (in its example, a geo map weighs 1, a table 0.6 and a chart 0.3). Size in MB and page weight measure different things, so look at both.
- Do not make “Don’t show this message again” the team default. The whole value of the warning is that it interrupts you. If someone turns it off, it should be a conscious decision.
- Have an administrator check the Activity Log from time to time to spot stories saved with known issues and prioritise their review.
My recommendation
Once your tenant is on 2026.20 (or QRC4 2026 if you follow the quarterly cycle), pick your three most used and slowest stories, run the size analysis and review the open recommendations. Within an hour you will know whether the problem lies in the story definition or in the data, which is the first question to answer before you change anything.
Sources
- SAP BDC – Object Size Manager in Stories: Guided Path to a Leaner Story (SAP Community, 16 Nov 2026)
- SAP BDC - Performance Recommendations on Save: Proactive Guidance for Story Creators (SAP Community, 16 Nov 2026)
- Use Performance Insights and Story Object Size to Analyze Your Story Performance (SAP Help)
- View Performance Recommendations to Optimize Your Story Design (SAP Help)
- Apply Best Practices for Performance Optimization in Story Design (SAP Help)
- About Advanced Mode (SAP Help)
- What’s New – 2026 Releases (SAP Help)
- What’s New Viewer – Stories (SAP Help)


