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.

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.

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) .

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.

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.

Hi Team,

I would like to request the functionality to allow the Kendo UI Grid to scroll up to request the next page of data.  This would allow the Grid to show new items to first, and older items to be requested upon scrolling up.

Thank you!

Provide build-in support for filtering and sorting for complex columns like dropdown or Autocompelete with dropdown in grid. Bound value consists of complex objects - one for value and one for text of the dropdown. Right now, sorting is based on value and not text. Please provide options to sort based on text. Filtering doesn't work for these columns. It would be nice to have filtering support for these columns.

Autofitting grid's columns according to its contents might be a pretty expensive operation, especially if there is are many rows. 

How about extending the 'autoFitColumn' function by a parameter which specifies how many rows should be taken into account when determining column's width. That would speedup autofit operations while maintaining a pretty good (good enough) estimation on column's width.

Hi Team,

I'd like to request the functionality to add an unsort option to the Kendo UI Grid's Groupable sort direction.  

Thank you

Currently the only way to make column headers fixed and always visible as you scroll through a Kendo Grid is to make the height of the grid fixed. This doesn't allow responsive UI and dynamic sizing of the grid. I would like to see support for having fixed headers regardless of height of the grid, such that the grid may fill whatever container it's in and change size while allowing this.

This Telerik response confirms the current functionality:

https://www.telerik.com/forums/columns-header-always-on-top

We have a requirement from customers to allow date columns to be filtered by the following criteria:

- IsToday

- IsBeforeToday

It should appear the grid as follows:

This would mean the filter is based on current date, rather than a date selected in a datepicker.

Rather than ask for this specific functionality we would like to be able to specify custom operators for date. As per the link:

https://docs.telerik.com/kendo-ui/api/javascript/ui/grid/configuration/filterable.operators.date

You can currently only alter the text on pre configured operators. We would like to be able to add new operators, like this.

kendo.ui.FilterMenu.fn.options.operators.date.today = "Is Today";
kendo.ui.FilterMenu.fn.options.operators.date.lttoday = "Is Before Today";

We would then need to be able to configure the logic used for the new operators.

Currently with large number of records in the grid when column is resized quickly resize may not actually occur.In this case, the browser's JavaScript engine is not able to fire the appropriate events fast enough, due to the large number of records, which impose a performance hit on the page.
Suggested solution: 
it is possible to improve the column resizing performance if the columns are not resized real-time during dragging, but only after the user drops the resize handle.

when putting grid into new item creation state it should be possible to put new item with some predefined fields.

Current it is realy difficult to achieve that:

using datasource and insert do not contain isNew on model, also put it on top of grid page is difficult, not possible

using model.set. on edit event causing fireing save event when it should be fired only when item is realy saved.

Currently the new select column and the "selectable" setting of the grid are mutually exclusive.  This seems completly counter intutive.  If you you have a select column and the "selectable" mode set to "multiple", then when you drag select or ctrl click on row the checkbox to be selected.  Right now it's not.  

If another value gets created, we want to be able to update the columns.values array without destroying the grid and recreating it.

In the JQuery Grid if you have the following column definition (for example):

[
    {
        "field": "Name",
        "title": "Name"
    },
    {
        "title": "Address",
        "columns": [
            {
                "field": "Street",
                "title": "Number & Street"
            },
            {
                "field": "City",
                "title": "City"
            },
            {
                "field": "PostCode",
                "title": "Post Code"
            }
        ]
    },
    {
        "title": "Contact Details",
        "columns": [
            {
                "field": "Email",
                "title": "Email Address"
            },
            {
                "field": "Phone",
                "title": "Phone Number"
            }
        ]
    },
    {
        "field": "DOB",
        "title": "Date of Birth"
    }
]

When you drag the multi-column header "Address" and drop it over "Date of Birth" the header and it's child columns move as expected but the column headers in the two multi-columns get mixed up.

This only seems to happen when dragging a multi-column past another multi-column in either direction.

In google datavisualization grid, one can use cell formatters to add an excel type visualization to a cell. This could be a bar left to right showing the relative size of a value to the rest of the values. This could be an arrow comparing the result to another column either hidden or visible. This could be a color showing between red and green. The color could for instance get closer to red as they get more below 0. This is an amazing feature in google and easily configurable. It would be great of your grid could do the same.

Add property that defines a delay before requesting new items when scrolling. 

This would prevent sending multiple request when dragging the scrollbar and passing more than one page.

Add ability to have a horizontal scrollbar in the kendoui grid that appears at both the top and bottom of the data set to ease scrolling in large data sets.

We are running into a situation where our users need to copy values from a row in a Grid. The Grid also uses multiple row selection, and the allowCopy is getting in the way by copying too much data onto the clipboard. 

Would it be possible to set a field list in the options for allowCopy so that we can specify which columns are actually copied?

Example: 
allowCopy: {
  delimiter: '\t'.
  fields: [
    'column1', 'column2'
  ]
}

We are also running into another situation where we need to use templated fields, and allowCopy seems to be copying the cell text resulting in very ugly clipboard data. It would be nice if we could specify the datasource value to be copied instead of the cell text

Example:

allowCopy: {
  delimiter: '\t'.
  fields: [
    { field: 'column1', source: true },
    { field: 'column2' }
  ]
}

In both examples, the field name corresponds to the field name specified for the Grid Column.