Welcome to the Angular feedback portal. We’re happy you’re here! If you have feedback on how to improve the Angular, we’d love to hear it!

  • Check out the features or bugs others have reported and vote on your favorites. Feedback will be prioritized based on popularity.
  • If you have feedback that’s not listed yet, submit your own.

Thanks for joining our community and helping improve Syncfusion products!

1
Vote

The virtual scrolling feature in the Pivot Table component enables efficient handling of large datasets by rendering only the rows and columns visible within the viewport, thereby optimizing performance. However, a current limitation exists: it is not possible to freeze the row and column grand total values during scrolling when virtualization is enabled.

Current Behavior:

  • Virtual scrolling dynamically loads and renders data based on the scroll position using a three-page rendering approach.

  • For example, if the Pivot Table has 100 unique rows:

    • Only a subset of rows (e.g., 30) is processed at a time.

    • A smaller subset (e.g., 10 rows) is rendered in the UI.

  • Grand total rows and columns, which appear at the end of the Pivot Table, are:

    • Only generated when they scroll into view.

    • Not available for freezing at the initial render.

    • As a result, they scroll out of view, making it hard to reference them during analysis.

Enhancement Requirement:

To improve usability and analytical convenience, support should be added for freezing grand total cells during virtual scrolling:

  • Freeze row grand totals (typically displayed at the bottom) while scrolling vertically.

  • Freeze column grand totals (typically displayed at the far right) while scrolling horizontally.

Performance Consideration:

This enhancement should be primarily optimized for scenarios where the grand total position is set to Top (for rows) or Left (for columns). In such cases:

  • The grand total cells are readily available at initial render, eliminating the need for deferred data processing.

  • Their position and values can be cached and reused during subsequent runtime actions (e.g., scroll, expand/collapse, filter).

  • This approach will further improve performance and reduce redundant computations.

Expected Outcome:

  • Grand total cells remain fixed and visible during scrolling operations.

  • Virtual scrolling performance remains intact and optimized.

  • Feature support is consistent across all configurations, including row/column grand totals positioned at Top/Bottom and Left/Right respectively.


Image