SAP Analytics Cloud (SAC) is SAP’s cloud-based Business Intelligence platform that provides a range of analytics and reporting tools. It is a fast-evolving product, which gets updated frequently.
In this blog, Kris van Brouwershaven takes you through the main takeaways from the latest release for SAP Analytics Cloud: QRC Q4 2026-release, which happened on November 14th & 15th, 2026.
The headline is AI: SAC now talks about agents. The feature we are quietly happiest about? Merged cells in tables. Yes, really.
Note: This blog keeps Enterprise Planning out of scope.
With the current rapid growth of AI, SAP’s focus is also on agents. Where an assistant answers a question, an agent gets a goal and works towards it in several steps. SAP introduced the following agents:
Create and manage analytics and planning models in SAC with natural language prompts. The same goes for analytic models in SAP Datasphere. The aim: less manual model configuration.
Built for story viewers. It turns dashboard data into executive-ready summaries in the Joule conversation. It looks at the current story page (widgets, filters, variables and KPIs), names key drivers through a Top Contributors analysis and can compare your company with peers using financial KPIs and external
Generates a complete story from a question. It combines a language model, analytic insights, your business context and patterns in the data into visualizations, trend analysis and actionable insights. Viewers and designers can both use it.
Creates private versions and simulations, updates plan and forecast data and checks whether a plan is feasible. More planning, so out of scope as well.
Since this is new functionality in a tool that is not yet available at the time of writing, this is purely speculative and based on information provided by SAP. Over time, we will discover what these agents actually do.
Generating a story is one thing. Making it fit your audience is another. With Joule you describe the change you want at design time and the story follows, without manual configuration.
What you can ask for, according to SAP:
Add, remove or replace dimensions and measures.
Apply filters, drill-downs, sorting and ranking.
Change chart types, number scales and decimals.
Combine widgets: one instruction can touch several widgets, or use data from one widget to adjust another.
Add annotations such as thresholds and reference lines.
These are first steps towards an agent that can fully build dashboards on command, according to your wishes and preferences.
This one lands in your inbox. SAC alert emails get a trend analysis written by a language model. It describes how the KPI behaved in the past, based on scheduled snapshot data, and highlights the key variations in report subscriptions.
Why does it help? An alert tells you something is off. The trend tells you whether it is a one-off or a pattern. That decides whether you act today or next week.
The analysis relies on snapshot history. If you’ve not kept any history, this functionality won’t work.
We will need to find out what the prerequisites are, since they have not been disclosed yet.
Note: These AI features rely on a language model, so check which permissions and licenses are needed, and where your data goes, before you enable them for end users!
Axis titles of all standard charts can now be customized from the styling panel. The default stays auto-generated, so nothing changes until you want it to.
Why will my story not save? Until now, you had to guess. Now SAC shows the total size of the story against the allowed limit. In multi-page stories you see each page with its size and percentage. Per page, the widgets are listed from largest to smallest, with their type, and you can jump straight to a widget from the action column.
In the past, this type of performance analysis was not great, but it did give an indication of where most resources were going. With this overview, it becomes easier to locate exactly which process, page or object burns through the most resources!
Save a story with unresolved performance recommendations and SAC now warns you that it can slow down loading for end users. From the dialog you can go straight to the performance recommendations panel, save anyway, cancel or return to the story.
Tables can now generate their own title, based on the selected dimensions and measures. The title updates when the data changes, until you edit it manually.
From then on, it is a fixed title, like it used to be.
Charts already worked like this; tables have finally caught up.
My personal favorite of this release. Tables that read like a report instead of an export.
This release can merge consecutive header cells with the same member into one. The table shows its structure, and your reader no longer has to scan the same word twenty times.
Opt-in per dimension: you choose which dimensions get merged, on the row axis, the column axis or both.
Label position: show the merged label at the first, middle or last position.
Note: This is an SAP image, so we do not have a practical example of this feature yet.
A restricted measure limits a measure to chosen members of a dimension, such as revenue for one cost center. Picking that member in a deep hierarchy used to mean expanding node after node. You can now switch the member selector to a flat presentation of the hierarchy.
It works when you configure restricted measures, cross calculations and other calculation types with a dimension member selection. And it matches what story filters and input controls already offered.
SAC extends its live data access to Databricks Delta Shares, the way Databricks shares data with other platforms. You connect a Delta Share as a live source for analytic and planning models, and the data stays where it is. No load jobs.
Note: As with other live connections, performance cannot be guaranteed, and combining it with other models remains to be tested.
SAC can now use an Excel file or list in SharePoint as a live source for analytic and planning models. Think targets, mapping tables, or that “temporary” list that’s been around for five years. No load jobs, no copies: SAC reads the file directly at runtime.
Just keep in mind: a live Excel file is only as reliable as the person editing it.
Our second favorite. Guidance inside SAC, instead of a separate manual.
WalkMe is a digital adoption platform: it shows users, step by step and inside the application, where to click. That beats searching a manual that nobody updated since the last release.
In SAC, this could help with onboarding new users or walking colleagues through a changed story. More about WalkMe can be found here: WalkMe: the Digital Adoption Platform for SAP and here: WalkMe with McCoy: The Game Changer in SAP Transformations
Filter by condition for the Table widget
Filter table from headers
Version semantics for SAP Datasphere analytic models
Horizon Morning as the new default theme
Edit story filters in view mode
Time member label control for tables
Cancel queued jobs in the Job Monitor
Excel add-in: variable prompt enhancements
QRC4 is the release where AI stops being a single button and becomes a set of agents: one that generates stories, one that refines them and one that summarizes them. Whether they are ready is the real question, so check the status of each before you promise anything to your users. Meanwhile, the quiet winners sit in the details: merged cells and a warning before you save a slow story. And with WalkMe, SAC finally helps people learn SAC.
Are you curious about the previous releases of SAP Analytics Cloud? Check our other blogs:
SAP Analytics Cloud QRC2 2026 – Optimize Your Tables & Extended Excel Integration
SAP Analytics Cloud QRC3 2026 – AI Integration & New Chart Types
Or would you like to know more about SAP Analytics Cloud or Reporting in general? Feel free to reach out to Kris van Brouwershaven.
As an innovation partner, we want to continue inspiring you. That's why we gladly share our most relevant content, events, webinars, and other valuable updates with you.