Problems in Kendo PivotGrid for JQuery V2

[JRC.T.6]

Hi there,

We face a few filter-related issues when exploring Pivot grid V2 and using the default configuration options.

1. When Kendo pivotGridconfiguratorV2 is not displayed we miss the opportunity to apply filters (that works in the legacy Pivot grid). Can you suggest a workaround or a config option?

2. When a filter is programmatically applied and the configurator is displayed, in the respective field dropdown this is still not reflected (prefilled), so the user wouldn't know a filter is already acting. That also works in the legacy Pivot.

 

3. For certain field types (e.g. number) the option to apply field filter is not provided at all, even when we have one programmatically applied already, only 'Include fields...'

 

Please, provide guidance on the issues above.

Thank you,
Georgi

 

[Georgi Denchev]

Hello, Georgi,

I'll get straight to the answers.

Custom Filtering UI

The PivotGridV2 has an updated UI and the filter menu is no longer present on the individual columns/rows, instead it is part of the configurator(as you mentioned).

If you wish to use a different type of UI, you'll have to create it manually. You can create a menu somewhere outside of the PivotGridV2 or use the Filter component to apply filters programmatically.

This is a bit of a hack, but you could clone the chips from the PivotConfigurator and insert them in the empty cell of the PivotGrid:

              dataBound: function() {
                let emptyCell = $(".k-pivotgrid-empty-cell"),
                    configurator = $("#configurator").data("kendoPivotConfiguratorV2"),
                    rows = configurator.rows.element.clone(true),
                    columns = configurator.columns.element.clone(true);
                
                emptyCell.empty().append(columns).append(rows);
              }

Dojo

https://dojo.telerik.com/@gdenchev/iGUyEjAB 

Programmatic Filters not Appearing in the Menu

This does seem like a problem, I'll report it to the Devs and let you know once I have more information on the matter but I suspect it is a bug.

Filter Menu Missing for Numeric Fields

There are certain limitations when it comes to the Local Binding, however I would like to double-check with the Developers if that is one of them as I don't want to mislead you.

Let me know if there's anything else I can do for you in the meantime.

Best Regards,
Georgi Denchev
Progress Telerik

[JRC.T.6]

Very cool "hack" Georgi, it could also be an enabler for us to position the filter menus outside the grid layout. Thanks! Is there a way to custom label the filter menus? (instead of defaulting to the underlying data field path and name)

The other hint for using standalone Filter components should also do the job for us.

In Pivot grid V1 numeric fields are fully filterable with local binding, it should normally work with V2 as well. As you suggest - please, check this with the Developers.

Best regards,

i Vesela koleda,

Georgi

 

[Georgi Denchev]

Hi, Georgi,

I am glad the examples have been of use to you!

The PivotGridV2 was rewritten from scratch with an entirely new engine so there could be some fundamental differences between the old and new widget.

Nevertheless, I'll speak to the Devs once they are back to work and I'll let you know as soon as I have more information on the matter.

Best Regards,

and Happy Holidays to you too!

Georgi

[JRC.T.6]

Hi Georgi,

I actually tried just recently your second suggestion - to use a Filter component - and, I am afraid to say, that it did not work as expected. The main reason, as much as I can gather, is that Filter component expects a DataSource, not PivotDataSource.

It may be that I miss something thou. Are there some examples demoing Kendo Filter component attached to a PivotDataSource?

Best regards,

and Happy new year!

Georgi

 

[Angel Petrov]

Hello,

Happy new year to you too!

I will start iterating over the points again to bring-up some of the details on them.

1. Indeed the approach with the Filter widget may not work. And here only programmatic addition of filters to the datasource will be possible. The new UI is strictly devided into displaying data(Pivot) and manipulating(sorting filtering and etc) data(Configurator).

2. This does seem like a bug can you please provide us with a code sample that we can inspect and validate its truthfulness?

3. Your observations are correct and the current state is caused by a design decision. We did wanted to check how the component will be consumed and how the developers will image the filter field would look like for the various data types. That said I would kindly like to ask you to open a feature request in regards of this in our feedback portal(if not already opened by other client).

Regards,
Angel Petrov
Progress Telerik