The Lite Weight Viewer (LWV) is one of the most impactful Client Side performance improvements SAP Analytics Cloud has shipped in the last few years. No configuration is needed for the viewer, it just kicks in automatically when a story is compatible.
That “when compatible” is where most stories are losing out.
Where we are today
Looking at our telemetry across the SAC landscape, one of the top three reasons stories fall back to the full viewer is Tables that haven’t been migrated to the New Table Experience. Stories with classic table widgets get redirected out of the Lite Viewer silently. No error, no warning, just slower than it could be.
For a refresher on what the Lite Viewer is and what conditions a story needs to meet, see the initial release blog post of the Initial Release of the Lite Viewer for SAP Analytics Cloud Stories
How to check where you stand
The Feature Adoption section in the SAP Analytics Cloud System Overview shows you, per folder, the share of story opens going through Optimized and Lite Viewer. If a folder shows a low Lite Viewer share despite being in Optimized Experience, classic tables are worth checking.
Start with your high-traffic folders. You don’t need to migrate everything, focus where it has the most impact.
Prioritizing what to migrate
A large tenant can have hundreds of Classic stories — most of them unused. Before touching tables, it’s worth separating what’s actively used from what can be cleaned up. The System Overview Housekeeping function and the Feature Adoption dashboard together give you that picture. For a practical walkthrough of that approach: Efficient Migration of SAC Classic Stories: Focusing on the Essentials
Migrating to the New Table Experience
With the 2025 Q3 QRC, SAP shipped a redesigned table building experience that is also what unlocks Lite Viewer compatibility. The migration itself is done directly in story edit mode. One thing to keep in mind: blended tables from the Classic Experience don’t auto-migrate and need to be rebuilt manually.
Full details on what’s new and how migration works: The New Table Building Experience in SAP Analytics Cloud
In short
- Check the Feature Adoption section in System Overview — look for folders with a low Lite Viewer share
- Prioritize: focus on actively used stories, clean up the rest
- For those stories: verify they’re in Optimized Experience, then check for classic tables
- Migrate the tables to the New Table Experience
- The Lite Viewer picks them up automatically from that point on
The Lite Weight Viewer (LWV) is one of the most impactful Client Side performance improvements SAP Analytics Cloud has shipped in the last few years. No configuration is needed for the viewer, it just kicks in automatically when a story is compatible.That “when compatible” is where most stories are losing out.Where we are todayLooking at our telemetry across the SAC landscape, one of the top three reasons stories fall back to the full viewer is Tables that haven’t been migrated to the New Table Experience. Stories with classic table widgets get redirected out of the Lite Viewer silently. No error, no warning, just slower than it could be. For a refresher on what the Lite Viewer is and what conditions a story needs to meet, see the initial release blog post of the Initial Release of the Lite Viewer for SAP Analytics Cloud Stories How to check where you standThe Feature Adoption section in the SAP Analytics Cloud System Overview shows you, per folder, the share of story opens going through Optimized and Lite Viewer. If a folder shows a low Lite Viewer share despite being in Optimized Experience, classic tables are worth checking.Start with your high-traffic folders. You don’t need to migrate everything, focus where it has the most impact.Prioritizing what to migrate A large tenant can have hundreds of Classic stories — most of them unused. Before touching tables, it’s worth separating what’s actively used from what can be cleaned up. The System Overview Housekeeping function and the Feature Adoption dashboard together give you that picture. For a practical walkthrough of that approach: Efficient Migration of SAC Classic Stories: Focusing on the EssentialsMigrating to the New Table ExperienceWith the 2025 Q3 QRC, SAP shipped a redesigned table building experience that is also what unlocks Lite Viewer compatibility. The migration itself is done directly in story edit mode. One thing to keep in mind: blended tables from the Classic Experience don’t auto-migrate and need to be rebuilt manually.Full details on what’s new and how migration works: The New Table Building Experience in SAP Analytics Cloud In shortCheck the Feature Adoption section in System Overview — look for folders with a low Lite Viewer sharePrioritize: focus on actively used stories, clean up the restFor those stories: verify they’re in Optimized Experience, then check for classic tablesMigrate the tables to the New Table ExperienceThe Lite Viewer picks them up automatically from that point on Read More Technology Blog Posts by SAP articles
#SAPCHANNEL