Limit the complexity of a Pivot Table field layout

[Ditchford]

Hello

In a Pivot table I want to stop the user from arranging the fields in the field list in a way that is going to hang the browser.  Is there a way to stop them from doing something too intensive.  I am already using the deferred layout, but I need a way of predicting that their design is just too much to expect from a web browser. For example, if their field design is going to result in (say) greater than 1000 cells (100 rows x 10 columns) then stop the pivot from trying to display (intercept the apply button).

Thank you.

[AngelinFaithSheeba PaulvannanRajadurai]

Hi Ditchford,

We believe that your requirement is to restrict the fields which has more members(combination has more rows and columns) while drag and drop the field or while clicking “APPLY” button of field list. If so, currently we don’t have option to restrict the fields dynamically based on the rows and columns count in the pivot table. However, you can use data compression, single page mode in virtualization and paging features to overcome the performance degradation while dealing with large data in our Pivot table.

Single Page mode and Paging:

Single page mode in virtualization and the paging features allows the pivot table to render only the rows and columns that are relevant to the current view page. This optimization significantly improves the performance of the pivot table during initial rendering and when performing UI actions such as drill up/down, sorting, filtering, and more.

Please refer the below documentation and demo to know more details about the “Single page mode” and “Paging”.

Performance demo: https://blazor.syncfusion.com/demos/pivot-table/performance?theme=fluent

Single page mode UG: https://blazor.syncfusion.com/documentation/pivot-table/virtual-scrolling#single-page-mode

Paging Demo: https://blazor.syncfusion.com/demos/pivot-table/paging?theme=fluent

Paging Document: https://blazor.syncfusion.com/documentation/pivot-table/paging

Data Compression:

DataCompression option works only if you have combinational data, because it compresses the data based on the uniqueness of the raw data, and unique records will be provided as input for the Pivot Table. The compressed data will be always used for further operations, reducing the looping complexity and improving the performance of the pivot table. Please refer the below documentation to know more about the “dataCompression” option.

Data Compression: https://blazor.syncfusion.com/documentation/pivot-table/virtual-scrolling#data-compression

We hope you are seeking for improved performance in Blazor Pivot Table; thus, we recommend that you experiment with the mentioned features of our pivot table. 

Regards,

Angelin Faith Sheeba.