As of the November 2021 release, ASP.NET Core introduces the new PivotGridV2 component, which, at some point in the future, will replace the old ASP.NET Core PivotGrid. This article explains the major differences between the two components.
- Why Do Two PivotGrid Widgets Exist?
- What Can I Expect from the New PivotGridV2?
There are many developers who use and depend on the PivotGrid. Making any drastic changes to the source code of the old widget would undoubtedly interfere with their work. That is why the decision to introduce a second widget, was taken.
The old and new versions of the PivotGrid can coexist. The old PivotGrid will not disappear with the upcoming release. This allows developers to smoothly transition to the new version without rushing their projects.
We have decided to keep the PivotGrid and introduce PivotGridV2 as a separate component. This approach allows us to avoid making breaking changes to the PivotGrid, which could affect many developers that use and depend on the PivotGrid. The old PivotGrid will not be removed in the upcoming release, which gives the developers the opportunity to smoothly transition to the new version.
The new PivotGridV2 has a new design, improved performance and is easier to customize.
The engine for the new PivotGridV2 is a cross-team development effort. It will be used by multiple different Kendo suites: JQuery, Angular, React, and so on. This approach will lead to the implementation of many new PivotGridV2 features, as all of them will be shared between the different products.
Performance is another key aspect that has been improved in the new PivotGridV2. Merging newly requested data on top of data that is already present, is considerably faster.
The new PivotGridV2 has a brand new design and some additional basic UX functionalities such as hiding the
configurator when it is not in use. This approach will provide the end user with much better experience when working with the component.
The new PivotGridV2 is easier to customize, when it comes down to functionalities such as data aggregation.
We encourage the developers that start new projects, to use the PivotGridV2 instead of the PivotGrid.
The following list summarizes the key benefits of the new PivotGridV2:
- Brand new engine, which allows for quicker implementation of features and quicker bugfixes.
- Improved performance of the component.
- Brand new design.
- Easier to customize compared to the old PivotGrid.
- Improved API, as new features are implemented.