I would like to see the ability to have more than one template for edit AND update on grid pop ups.  Currently I can set the template file for the editable option but that is also used for the create when doing a pop up modal.

Searching by date range is a very common use-case in most business applications. I need a From and To calendar controls in the row filter.

I would advise Telerik to put this functionality on the roadmap, else the row filter functionality is so restrictive as to render it useless. 

I am having to roll my own filters above the grid because of this one omission which is a real shame because the rest of the Grid functionality is so good.

(I don't want to use filters in column headers because I don't like the fact you loose visibility of what filters are on - probably the reason for the grid rows introduction)

Ability to set accesskey on toolbar actions without having to do a template.

It would be great to have support for all wildcards while filtering.

If an Ajax validation (sync or async) is called by a custom validation, kendo grid navigation should move to next or previous cell by pressing once tab or shift + tab key, if it's valid -as normally- or cancel edit if it is not.
+info in this thread:
http://www.telerik.com/forums/ajax-validation-with-grid

See this Kendo Forum post:
http://www.telerik.com/forums/multi-select-in-responsive

In short, we need additional approaches to grid multi select using touch events

Add a Title tag to grid headers so that if the user mouseouvers they can see the column title/filed name if it has been clipped by the ellipsis

The grid widget has a columns editor which allows a field to be a custom widget, like a drop-down list for an autocomplete. I want the title column to be selected from a drop-down list

Support custom attributes for Kendo grid
When kendo grid is applied to an html table, all custom attributes that have been applied to rows, cells or data within cells is lost.  It would be great if you could preserve these.  I realize the challenge in distinguishing between what is considered a *custom* attribute.  Perhaps enforce specific naming conventions and support preservation of those.  Perhaps anything starting with "data-" is preserved?

I would like to see the grid allow the adding of a new row via the keyboard when batch editing.

When the user is on the last row and last cell they can hit tab and the grid will add a new record and with focus on the first editable cell.

Or the user can hit enter anywhere on the last row to create a new row.

This would allow for rapid entry of several new rows of data. It would allow the user to key in data in a similar way a spreadsheet like Excel would behave.

In your article: http://www.telerik.com/forums/how-to-make-a-non-editable-column-field, many developers make the point that the read-only attribute of a column should be part of the view, not model/data.
By not providing a column property to prevent editing, you have put the view logic in the wrong place.
Solution: Create a read-only property to each column to prevent editing.

Many of us are wondering (http://www.telerik.com/forums/dynamically-add-new-column) how to add new column to grid.

I imagine it to work as column picker in TeamPulse (http://demos.telerik.com/teampulse-demo/view#backlog)

For now we have two options:
-destroy old grid and create new, but this way we must take care of bindings, event handling by ourselves.
-hide unwanted columns at start and then show them when needed, but this way DOM will have unused elements.

Ideally grid would reconfigure and add DOM for new column.

Ext.JS has this build in (http://jsfiddle.net/marcusschiesser/GvGCX/)

Instead of having to do this or something similar to this ...

function (container, options) {
    $('<input data-text-field="' + options.field + '" ' +
            'class="k-input k-textbox" ' +
            'type="password" ' +
            'data-value-field="' + options.field + '" ' +
            'data-bind="value:' + options.field + '"/>')
            .appendTo(container)
}

add a type "password" to the grid and let the js do it without having to code :)

For string columns especially, the default type of filter someone would want to apply is not the first option in the list. If it's not possible to reorder the items, then it should be possible to select which item is the default. This would prevent users from having to change the filter every single time.

It would be like to setting the Edit Row and Filter Row to support checkbox without ClientTemplate. It is a very very common editor type for boolean field.

On Kendo Grid, It will be nice to use a combination of Server and Client side code for pagination and sorting.

I want to limit the number of rows pulled from the server by 2000 rows. On the screen, the grid can be set to a page size of 20. If the actual rows are less than 2000, there is really no need for the grid to call the server again for paging or sorting

If you are on the last page of a set of data and delete the last item from the page the pager does not reset to the previous page. This seems like an obvious bug to me.

Steps to reproduce:

Go to Grid Demo: http://demos.telerik.com/kendo-ui/grid/editing-inline
Select "Edit this example"
Change the pageSize of the dataSource from 20 to 2
Run the demo
Go to the last page
delete the two items on the page

Result: Grid does not move to previous page and incorrectly displays the item number as higher than the total number of items.

I know it has been rejected and I think it was not given any good reason.  Managing dropdownnlist in datagrid is a pain and just not having pair value/text is missing and using "foreign key columns for this" is not an acceptable answer for me.


It should be a basic type of column, not a template, and show a text but be set as a value because we use the text for translation purpose, so the text cannot be the value. Even with the help from your technical support, when you have many of them in one grid, it's takes a long time to code and maintain. Such a common and basic feature should be with the basic controls of the grid.

Allow the use of a custom filter function for a given grid. operator could be assigned a function to perform the filtering. 
        var filter = {
            field: field,
            operator: function(row, column, filterUi) {
                var fieldValue = row[column.field];
                return matchesArbitratryCriteria(fieldValue);
            },
            value: value,
        };

The current table initialization used in grid is not robust and does not supports many features. The main reason is because _columns function in grid does not leverages existing framework functionality. I propose to slightly modify the existing code responsible for parsing column configuration to use kendo.parseOptions instead of working directly with attributes. You can see my re-implementation of this function at [http://jsbin.com/pihefuva/1].