Skip to Content
Product Information

An Improved Table Experience

In the past months, we received a lot of user feedback for the table widget in SAP Analytics Cloud – from long loading in-cell charts to different row heights or an unpleasant scrolling behaviour. Of course, this is not what we would like to hear, so we had to act. Now with wave 2020.05 we are delivering the following improvements:

Smooth scrolling 
Scrolling is an important function in tables as we usually display more than a couple of rows or columns. The scrolling behaviour was column and row based, now we changed it to pixel based. This feels much smoother and natural for the user, especially on mobile devices. The viewer of a story or application can scroll by hovering over the table and there is no more need to click into the table.

Faster loading In-Cell charts and thresholds
With just one click the values of a measure can be turned into a chart. But the loading times of the little bar charts were a big pain point. Now we have implemented a much-improved solution that gives users an optimal performance.

Consistent row heights 
Row heights sometimes varied when users were drilling down in the table. Now all rows are always equally distributed. Also, the designer can set the row heights in the styling side panel to a custom height or use predefined FIORI heights (Default, Cozy, Condensed) which are adopting automatically to the used font size.

Responsive vs. Unresponsive
We simplified the responsive logic of columns that all content is always visible. This might lead to wider columns with a horizontal scroll bar. To reduce the width a wrap on the column can be used. In case the columns are not fulfilling the whole table size, the leftover white space is distributed evenly.

The unresponsive logic is made for a pixel perfect design. The designer can resize single, multiple or all columns at the same time and specify the width to an exact pixel value.

Table title 
The table title will be always shown and does not scroll with the content anymore. Its height is automatically adjusted to the title’s font size. Of course, everyone can still hide the whole title via the context menu if not needed at all.

Linked analysis 
For tables using linked analysis, CTRL + left mouse click now deselects a member and ESC clears the whole selection.

How to try it out
We decided, for now, not to make these changes as default as we are working on more improvements in the upcoming waves. Nevertheless, there is no big deal in trying it out. In the table’s builder panel, the designer can select the checkbox ‘Beta Table’ and all new functions are directly available.

Further information are available behind the little info icon next to the check box or on our SAP Help portal. Have fun!

You must be Logged on to comment or reply to a post.
  • Nice to see feedback in action, Steffen! When are you pulling the trigger in replacing the old Table Design? Will old stories be updated automatically (super important imo!)?

    • Hi Moritz,

      next goal is to get rid of the current limitations and make it the new default behavior (flag enabled when creating a new table). For existing tables you will then be able to use the story preferences and switch all tables to the new behavior with 1 click.



  • Excellent news!!

    This is by far the weakest point of the product, especially with BW Live connections.

    For which Wave are these improvements planned? Will it alternatively be deployed via patches?


    And inded, please be sure that existing tables won’t break (anymore). 🙂

    This is forcing us to spend many hours to make sure that new releases or changes in stories or even sometimes simple navigation don’t break tables, formatting, even whole stories.

    A question: Can anyone recommend any automated testing tool for SAC (and Live connections with SSO)?


    • Hi Inigo,

      the improvements were deployed with wave 2020.05 for fast track customers (released March 15). This ends up into the May release for quarterly updated tenants.

      As we need to set this flag manually, there is no disruption to any existing tables.I know that the impression might be different, but believe me priority number 1 is not to break anything as this hits all of us hard. 

      Thanks for your feedback,

  • Hi,

    Great news!

    I’m checking it on my tenant (2020.6.3), my findings are:

    1. I can’t resize column widths.
    2. In-cell chart performance is much better.
    3. Scrolling with high number of rows is still not smooth.


    • Hi Erdem,

      thanks for your feedback. To your points:

      1) For responsive logic we simplified the logic to show all content and adopt column width automatically instead of manual resizing. Unresponsive column width allows pixel perfect resizing.

      3) A high amount of rows might lead to some hickups when requesting the next batch of rows. We are continuously working on enhancing this behavior and performance overall.



      • Hi Steffen,

        When column widths can not be resized, wrapping is also handled after a chracter limit I guess.

        It will be necessary to set the wrapping point manually.




  • Hi Steffen

    Do we have any data volume recommendation for populating Table, Or do you see any benchmark number, where we can say post “n” number of records, scrolling will get impacted or response time will go down. I am asking this question because we are positioning Operational Reports Scenarios in SAP SAC instead of traditional BOBJ tools. Do you see any challenge in these Use Cases.


    • Hi Tarun,

      we have a safety belt of 30k cells which can be extended when reaching that limit in the table details. In general more rows and columns lead to more time spent on requesting and rendering the data. What amounts of data are you targeting to display?

      My colleagues from the Web Intelligence team are currently working on reporting in SAP Analytics Cloud, so we are definitely targeting this scenarios as well.


  • Hi Tarun,

    I see the improvement in the scrolling which is a good start.  My main issue with the table component, still present in Beta mode, is that when you have a measure it always has to be on the far right of the table.  Also when adding the measure it adds ‘Measures’ label and the actual measure name is not aligned on same row with the dimension headers.  This also then causes problems when exporting to excel as shown in screenshot where filters should be on same header row.  Is product group working to have dimensions and measure on the same line for the header?

  • Hello,

    I have the same problem as Christopher, when I export the table to Excel file, the file contains 2 rows: one for dimension headers and one for measure headers. After it is necessary to modify the file manually.

    This issue also exists when I export the table to CSV file (2 rows for the headers).

    I hope it can be fixed in new waves. Thanks.