I want to sort rows and columns by values (not fieldnames). One way to do that is like it's done by DevExpress (https://demos.devexpress.com/ASPxPivotGridDemos/OLAP/Browser.aspx). By right clicking a field i can choose for with field, row, column and measurement i want to sort. But even this solution could be more userfriendly. Another more direct solution would be to sort by clicking on a measurement field or if there is only one, on a fieldname. Both are just suggestions. But the functionality of sorting by values is really relevant. http://www.telerik.com/forums/sort-rows-and-columns-by-values
Problem: The values and fieldnames can be very long or very short. Based on that, values and fieldnames are often truncated or lost in a way to wide column. That behavior has many downsides: - The PivotGrid need much more space then it should - Long values and fieldnames can't be read - It's totally not responsive and looks bad Competitors solution: - http://www.igniteui.com/pivot-grid/all-grid-features - http://webix.com/pivot/ Problem-solving approach: - Show resize icon when hovering over a the bar between two columns - Resize this column to it's min. width (value or fieldname) after a double click on this bar - Manual resizing of the column by drag and drop of this bar - Automatically size columns to there min. width on initialisation
You really need to add sorting to your Kendo UI pivotgrid for flat/local data sources. The entire point of a pivot grid is to analyze data. We did a POC with it for our salesmen. The feedback was: "It's almost useless if I can't sort it and see my top and bottom sellers, etc...". So, we're swapping out the pivotgrid for Infragistics Ignite UI. It's a shame too, cause most everything else is there.
I would like to see a persist state feature like in the grid control applied to the pivot grid. A complex cube state is difficult for our users to set up each time the page is loaded. It would be great to save the current state of the pivotgrid and restore it on future visit.
The PivotConfigurator is very static. It would be nice to change the layout. For example some options: - Hide / visibility of all four elements (Row, Column, Measure, Fieldlist) - Position of all four elements (Row, Column, Measure, Fieldlist)
Currently Pivot Grid has very limited support for flat data. Please include a library so we can emulate OLAP on the MVC controller side for the FLAT data and can use full features of the PIvot Grid. OR somehow fully support the FLAT data in Pivot Grid (including Configurator, Filtering etc)
We have an existing application that was developed with ExtJS, that we'd like to move to AngularJS+KendoUI. The only thing that's holding us back is that you don't have the ability to created editable PivotGrids. That feature is available in Sencha's product, and our users use it extensively. Ex: http://examples.sencha.com/extjs/6.0.2/examples/kitchensink/#rangeeditor-pivot-grid
Expanding programmatically all paths in a level in a pivot grid is coumbersome. One should be able to expand all itlems in a level. Also when one row.expand and column.expand configuration should work for all levels.
Currently there is no way to select database and cube in the analyzer. http://demos.telerik.com/kendo-ui/pivotgrid/index Please consider this functionality.
Kendo pivotgrid does not allow us to hide 'All' row/column.'All' row/column is not always needed in a OLAP report. Excel would allow us to hide/eliminate subtotall rows/columns. pivotgrid needs similar functionality. In general emulate Excel pivotgrid functionality in kendo pivotgrid
In SSAS world you can often see mega cubes with many measures and dimensions. Currently Kendo pivot grid configurator does not show measure groups and therefore there is no way to filter dimensions and filters that belong to a specific measure group.
Now if you set filterable true for KendoPivotGrid you get two options - Include Fields and Fields Filter. In some cases you need only one of this options and it is not good to be with one option - filterable.
In some applications data will be so huge to load on PivotGrid, and the manipulation of filtering, reordering and changing dimensions between rows and columns take a long time, freezering the browser for a moment. With data paging this frozen time is avoided.
Kendo pivotgrid currently has only row and column filters. Filters and Filter area are also important. See other pivotgrid implementations - especially DevExpress ASPxPivotgrid and Excel pivot table
What we would need is te possibility to show the percentage of the gand total summary. For example: row / column value 1 / 2 2 / 3 3 / 5 summary / 10 => change calculation to percent of grand total 1 / 20% 2 / 30% 3 / 50%
At the moment it's possible to drag & drop fields into the grid. But it's not possible to set the field at a specific position. That is very unusual. I would expect to see a position marker while hovering with a fields over the drop area. When ein drop the field it goes there where the marker was.
An OData feed that supports 'OData Extension for Data Aggregation Version 4.0' can be queried for all of the information required to populate a PivotGrid with rows and columns that are paged, sortable (including by different aggregates of the measures), and filterable, and have all calculations performed on the server. The pivot grid can be popualted using data obtained from a couple of requests to a suitable feed -- or feeds. Suppose we have an OData feed that we'd like to display in a pivot grid. Some of the columns in the feed will become dimensions, and some will become measures. (We may display the same measure more than once, with different aggregates applied.) In order to display the row/column headings for the pivotGrid we need to select the distinct values from the 'dimension' columns. The filtering provided by OData allows the row/column headings to be filtered, and even paged (in both directions). Sorting is more difficult because we want to sort not only by the row/column heading values themselves, but also by (aggregates of) the measures. However, that's a problem for the server side! In order to populate the body of the table we need to calculate a load of aggregates from the measure columns in the base dataset for the rows that correspond to visible row/column headers. We can write a rather long OData $filter expression to obtain the required rows from the original OData feed, and then aggregate them. All of this functionality is available in 'OData Extension for Data Aggregation Version 4.0'. However, as an interim solution we may establish two 'helper' OData feeds associated with the original feed: one for the dimensions for populating the row and column headers, and one for the measures to populate the body of the table. The grid has already established a convention for asking for aggregates computed on the server, although this can be overridden using parameterMap anyway.
As per this post: http://www.telerik.com/forums/pivotgrid-bug When using PivotGrid with a flat data source the handles for dragging the dimensions are labelled with a different string to the dimension headers. The dimension headers are labelled with the dataSource.schema.cube.dimensions.[name].caption. The dimension drag handles are labelled with the dataSource.rows.name (or dataSource.columns.name). Now, the dataSource.rows.name must be the key in the dataSource.schema.cube.dimensions of the dimension and this must also be a key in each item in the data array -- the field that stores the value of the dimension -- and therefore is in general not suitable for showing to users. In any case, it seems to me to be a bug that the drag handle is labelled with a different string to the dimension caption.
Currently the Kendo PivotGrid always starts out with one tuple for each dimension on rows and columns, and you can recursively expand members to get to their children. However, even with a moderately deep hierarchy, this quickly consumes a lot of screen real estate. It would be useful to have the option to drill-down in addition to expand. I understand that it's not an easy feature to design and implement, mainly due to the merging of cells that occurs when expanding, which is also the reason why the grid must always have one single member on the first level of a dimension on rows/columns; but I'm hoping someone can come up with an idea that would make it easier. Cheers!