Handling Dimensions with Lots of Data

[Steve]

I'm looking at using the Pivot grid to allow some simple data analysis, attaching to an OLAP data source using msmdpump.  One of the dimensions of the cube I am working with has rather a lot of rows (~15000) which is giving me a performance problem.  Typically users would only want to compare 3 or 4 of these rows - but the dimension filter doesn't seem to handle such long lists of options.  Similarly, expanding the whole grid with that dimension selected isn't really an option, as no one could sensibly use 15000 rows of data, even if they could be rendered in a timely manner.

Is there some way to just request a subset of a particular dimension from the cube, so that users could preselect the information for that particular dimension, allowing the Pivot Grid itself to deal with more sensible data sizes?

[Georgi Krustev]

Hello Steve,

One possible solution in this case is to use filter the PivotDataSource manually, thus starting always only from the required subset of data. Here are two examples how to filter the source using API:

• http://docs.telerik.com/kendo-ui/controls/data-management/pivotgrid/how-to/filter-dimension
• http://docs.telerik.com/kendo-ui/controls/data-management/pivotgrid/how-to/filter-dimension-with-include

If you would like to allow a dynamic filtering, then you can build a separate filter form next to the pivotgrid and use the API of the source to apply the required filtering.

Regards,
Georgi Krustev
Telerik

 

 

[Steve]

Georgi,
Thanks for getting back to me.  I tried using filtering in the way you suggested, but found that the filter only worked for the initial page load.  If I then dragged another measure onto the pivot, the filter appeared to be cleared, so that all the data was returned again.  Is there something I need to do to ensure that the filter is applied on all subsequent requests as well?     

[Georgi Krustev]

Hello Steve,

Currently, the PivotGrid is designed to reset its state (filtering, sorting and etc) when its column/rows/measures structure has changed. This is done in order persisting an incorrect state. We have plans to make that state reset more refined and hence to keep the state of the unchanged dimensions.

For now you will need to re-apply the filtering expressions manually. You can do that using the dataSource.filter method:

• http://docs.telerik.com/kendo-ui/api/javascript/data/datasource#methods-filter

The format of the expressions are like in the configuration filter option shown in the how-to demos.

Regards,
Georgi Krustev
Telerik