nnguyen95
Cloud Apps
Joined 3 years ago
User Profile
User Widgets
Contributions
Freezing pivot table header rows without manually resizing widget
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.2.2KViews18likes7CommentsFreezing header row in pivot table
Hello, I've researched the past discussions for this question and did see that the advised solution was to disable the pivot table's Auto Height setting and adjust the height of the widget until a scroll bar appears for the pivot table, separate from the dashboard's scroll bar. In testing this solution, I've found that it is difficult to scroll to the bottom of the pivot table's scroll bar and view grand totals without also scrolling down on the dashboard, requiring the user to scroll back up in the dashboard to view the bottom of the pivot (see "Pivot_ScrollBars" attachment for how this generally looks). This is the main usability issue I've identified with the advised solution, so I'd like to see if there may be another way to accomplish freezing a pivot's header row which could potentially avoid this. Thank you!814Views0likes0CommentsRe: Tracking Metrics Before and After Change Point
Hello, Unfortunately this solution was not exactly what we were looking for. We ended up using a workaround and calculating the metrics before and after the change made on the Config Start Date by pre-calculating these in SQL using the LAG function. However, we'd like to see if there would be a way to solve this without pre-calculating in SQL. Is there any functionality in the Sisense formula builder that could potentially emulate the LAG function in SQL? This is what we were hoping to achieve using the PREV function, but as noted in Lily's response this is not how the PREV function works in actuality. Please let me know if any further information will be needed. Thank you!1.7KViews0likes0CommentsTracking Metrics Before and After Change Point
My team and I are currently working on a pivot table where we track how slot machines are performing based on their Stand ID (denoting a location on a floor), based on changes made to machines at that location. The "ChangesPivot_v1" attachment shows our first attempt at this, where the Stand Config Version number changes every time any change is made to the machine. The version number is based on a start and end date for that particular configuration. Metrics and changes between configurations are expressed in multiple rows, one for each machine configuration. To highlight a specific example, we would consider a change to have occurred on 3/10/2023 in the "ChangesPivot_v1" attachment. Prior to the change on 3/10, this machine recorded $2,199.14 in Win. After the change, from 3/10-3/13, this machine recorded $1,578.11 in Win. The request was made to consolidate these and present metrics broken up into before and after a particular change is made. Our attempt at this is shown in the "ChangesPivot_v2" attachment. We attempted to display the Win recorded for a given Configuration (denoted by the start date), then the Win recorded for the previous configuration. To accomplish this, we tried using the PREV function in the widget editor (please see "Prev_logic" attachment). However, this is not giving us the results that we expect. In the v2 screenshot, for the change on 3/10/2023 we would want the Win column to show $1,578 and Previous Win column to show $2199 ideally on the same row, but we're not getting the results we would like. Is there potentially a better way to go about accomplishing this? Please advise if any clarification will be necessary. Thank you1.9KViews0likes3Comments