For performance reasons, we would like to only show the group headers collapsed when first grouping, and only add its child rows when expanded. This is done for hierarchical grids and minimizes unnecessarily large DOMs for data the user will never look at. 

It would be nice to have the progress when exporting the grid to excel so that the user knows that something is happening.

Consider a grid with grouping and pagination. When we collapse a group, the items from next page should take up the space left be the hidden rows, i.e., grouping should work across pages and not just the current page. Otherwise, grouping is a useless feature in a grid with pagination. This should work for client as well as server pagination and also for virtual scroll.

When using a screenreader in navigate mode the grid does not announce that the column headers are links that can be used to sort the table.  There are aria-label tags added when a grid grouping function is active (like the demo at https://demos.telerik.com/kendo-ui/grid/keyboard-navigation), but there is no aira-label text to indicate the sorting behavior. 

Hi Team,

I would like to request the functionality to sort the  MultiCheck Filter for the Kendo UI Grid. For example, maybe adding a columns.filterable.sort property. 

Thank you!

  

It would be nice if its possible to slide threw the pages in a grid by using a slider in the footer.

Updating a single row by default expands ALL collapsed groups. Removing a single row or inserting a single row does the same. This design lacks granularity: an isolated change to a single row should not cause the expanded/collapsed state of all groups to change.

If the user is focusing on flu cases in New York City and a new flu case is added to the Los Angeles group, why should every group in the grid be expanded? 

 Only the group affected by the change should change its UI state. The grid should listen for the change event of the observed  *row* and if it is felt that a change to the row's data should cause a UI change, only the group to which that row belongs should be changed.

The grid popup editor is great but when you have a large number of fields to edit the height of the popup window becomes impractical.

What would work much better would be to split the single column of fields into two or more columns making the window wider but shorter and ultimately more manageable.

Maybe the popup could have a "columns" configuration option to allow for this type of functionality.

I know it is possible to show/hide columns through the column menu, but there is something odd about being able to hide one column from another column's menu. Alternative is to implement something yourself and use the API to show/hide a column, this seems like something that should be an option in the grid. I am imagining a column chooser button (perhaps in the top left header) that opens up a list of checkboxes similar to what you see in the column menu.

New items (rows) are not shown in grid when they don't match the filter settings made to the grid.
So it would be really useful if applied filters and sortings were resetted when new items are created.

We have a problem when working with grid in batch edit mode which puts different fields in the In cell edit mode.

The problem is that cell that are not edited (for example you create a new row, edit only the first field, press save) are never validated. This is of course because they never went into edit mode, so the control and validation was never rendered.

Please give us a feature for such scenario.

Highlight a row during mouse over has to be done through CSS. However it doesn't work properly when there is a locked column, as there are two separate tables. This requires some programming. I suggest you embed it in Kendo, so we could easily use this feature without having to implement it ourselves.

In addition to columns.minScreenWidth, the grid also needs columns.maxScreenWidth for the situation described here: 
"http://www.telerik.com/forums/need-columns-maxscreenwidth-too!"

Thus avoiding the need to work around the timing problem with a timeout like this:
columnReorder: function(e) {
 setTimeout(function() {
                // save data logic implementation.
            }, 100);
}

It would be nice to have the option to configure different column titles for the column menu. For example, when there is a multi-header Grid, you could use this functionality to add the header title to the column title.

https://www.screencast.com/t/qgeK9fFMPP
https://www.screencast.com/t/NRl61JFzFH

At the moment, Remote Validation on the grid does not work with incell editing.

I would like to see this restriction removed.

Normal validation works with incell editing; however, the remote does not. I should not have to change the appearance and functionality of the grid from incell to to inline just because the standard validation is insufficient.

I appreciate that this is not an easy change, but hope you are able to give it some priority.

Kendo grid doesn't have in-built functionality to prevent row selection based on some condition.
One way is to remove css class "k-state-selected".
But i think there should be something like "changing" event which will be called before "change" event.
In that event developer write code and can cancel "change" event.
Or 
Boolean property something like "enabled" at row level (or cell level for cell selection) .

The existing configuration(filterable.extra), can only support 1 or 2 input from the UI. It would be great if multiple filter criterion input from the grid UI will be supported in the coming releases.

The Grid already has beforeEdit event that can be used for preventing the editing depending on custom logic. The same thing could be used for preventing add or delete based on custom logic or validation.

It would be nice to have the option for a single filter input that searches all columns on the Grid.  I was able to implement my own custom solution but having to apply that to every grid in my app is cumbersome.

I understand the importance for the flexibility side of having each column with its own filter box, but for simpler apps this is overkill and a single filter box is enough.  The column component already has the [filterable] flag so this can possibly be used to exclude any columns if necessary.

I was thinking of something similar to what is an out of the box feature for the Datatables JS plugin

https://datatables.net/

Default search box that searches everything.  Very simple to use and understand for basic users or when your application only calls for something that simplistic.