Freezing pivot table header rows without manually resizing widget

[nnguyen95]

Sisense does not currently offer the ability to easily freeze the top row of a pivot table, similar to what most spreadsheet applications offer.

Prior community questions on this topic (such as https://community.sisense.com/t5/build-analytics/freezing-the-header-row-for-a-pivot-table/td-p/3022... advise a workaround by manually disabling the Auto Height feature for the pivot table widget, then reducing the height of the pivot table until a widget-level scroll bar appears. 

This solution only works for a very specific use case, and losing the ability for the widget to dynamically resize when populated with different sizes of datasets and/or when applying dashboard-level filters makes it less tenable. For example, if a widget is manually resized so that the header is visible when scrolling for 50+ rows of data, the widget will stay the same height if a filter is applied that reduces the dataset to 15 rows.

We'd like to see if there is a way to easily freeze the header row of a pivot table while preserving the ability for the widget to automatically resize based on the amount of data. Ideally this would be a checkbox or other easily accessible widget-level setting.

[OleksandrB]

We need a code or possibility to freeze the first column of a pivot table. So that when the user scrolls right they can still see the main column.

[kingsofdeleon]

Piggy backing on this,

Adding a pivot table design option in the design editor that allows us to select what number of columns to freeze (Starting from the left).

[dougnewton]

Yes!  I was just wishing for this the other day.  As the OP noted, this is a pretty standard sort of feature in BI applications, and shouldn't require writing additional "code" to implement.

[MikeGre]

Yes, we recently got a similar question if this was possible. It would be nice to have!

[MikeGre]

@nnguyen95 @dougnewton  try this: 

https://community.sisense.com/t5/build-analytics/freezing-the-header-row-for-a-pivot-table/m-p/3022

It worked for our use case 🙂

[DRay]

Thank you for sharing your idea and providing details. We will bring this to the product team and provide updates here as they are available.

We encourage people to continue to vote and comment. We use community interest as one of the ways we prioritize efforts, so every vote and comment can help turn a request into a reality.

Thank you again for sharing and being part of our community!