global option for grid colums that sets the format of number editor ui

Refresh Event Handler for refreshing the grid with refresh set to true

Drag fill multiple cells like excel. Kendo Spreadsheet control already has it. This is a crucial feature missing from versatile grid , IMO

Add a new attribute columns.command.materialIconClass and render it e.g. as <i class="material-icons">contact_mail</i> 

Example: 

var grid = $("#grid").kendoGrid({
                        dataSource: {
                           pageSize: 20,
                           data: createRandomData(50)
                        },
                        pageable: true,
                        height: 550,
                        columns: [
                            { field: "FirstName", title: "First Name", width: "140px" },
                            { field: "LastName", title: "Last Name", width: "140px" },
                            { field: "Title" },
                            { command: { materialIconClass: "contact_mail", text: "View Details", click: showDetails }, title: " ", width: "180px" }]
                    }).data("kendoGrid");

With out using the group column header(columns.columns). it is better to enable one option to keep some of the columns locking together in the grid. If you reorder one column other columns should move with it like that. When we use the columns.columns option we can't find the columns under that header using the column Index (column[index]) option.

Current, if one were to use the Kendo Grid in UI for MVC, there's no way to bind the datasource using Ajax binding and specify server side parameters to the read function in the controller.

In many cases, the read function on the controller side will use a primary key to do a select statement to get particular details of a model to render.

This is relatively simple to keep track of on the javascript side and server side when there's just one grid, as we can use a hidden input and always update it's value from the model.

However, when we have an array of grids, and an array of primary keys for the grids, this is very difficult to keep track of which read function corresponds to which grid.

The only solution is to generate multiple javascript read functions with the primary key baked into the names and in the bodies of the functions on the server side, which is ugly and not optimal for security.

    @foreach(var modelID in Model.ModelIDs)

    var readFunction = "function modelStatsReadData_" + modelID + "()";
    <text>
    @readFunction
    {
        return {
            modelID: @modelID
        }
    }
    </text>
    } @*end foreach loop*@


@foreach(var model in Model.Models) 
{
....

                    .DataSource(dataSource => dataSource
                    .Ajax()
                    .Model(model =>
                    {
                        model.Id(m => m.ID);
                    })
    				.Read(read => read.Action("FlowPlanDetails_Read", "SubmitFlow").Data("flowPlanReadData_" + @model.D))

}


This is solvable if we do server side binding for the datasource, as we can pass route values. But that is an entirely different implementation and we shouldn't have choose Ajax() versus Server() binding based on how functional the API is.

Currently, there's no way to pass variables into client footer template functions that are registered with client footer templates.

In the case when you have multiple grids on the same page with different grid ids, you are forced to instantiate multiple javascript callback functions with the grid id/name baked into the function.  

Consider:

             @foreach    @foreach (var model in Model.MyModels)
             ...
             ...
             @(Html.Kendo().Grid<eFHOL.Models.ViewModels.MyModelModel>
                    ()
                    .Name("ModelGrid_" + @model.ID)
                    .Columns(columns =>
                    {
                        columns.Bound(m => m.Name).Width(30).ClientFooterTemplate("#= footerLabel(data) #");
                        columns.Bound(m => m.Hours).Width(30).ClientFooterTemplate("#= HoursSumAvg_" + @model.ID + "(data) #");
                        columns.Bound(m => m.Weight).Width(30).ClientFooterTemplate("#= WeightSumAvg_" + @model.Weight + "(data) #");


And you will have to have server side code to register and wire up each of these distinct javascript footer template callback functions:

    @foreach(var modelID in Model.ModelIDs)
    {
        var hourFunction = "function HoursSumAvg_" + modelID + "(model) ";

    <text>
    @hourFunction
    {
        var grid_name = '#FlowPlanDetailsGrid_@modelID';
        return HoursSumAvg(grid_name);
    }


This quickly becomes a mess if you have a for loop that renders 5 or 10 grids, as we have the use-case for. 

It would be very helpful if there was a way to register the name of the callback which accepts server side parameters that can be evaluated on the server side and passed to the javascript function.

Alternatively, if the client footer template functions could somehow retain the name of the grid they are bound to, via a property in the parameter passed in, that would be good enough.

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.

Currently in a data grid with virtual scrolling there is no way to scroll to an item. You can filter to that item, but you can't see it in the context of other data. I'm pretty sure this was available in Silverlight rad grid 7-8 years ago.

Show the text in the filterMenu formatted as the text in the column. More info here: http://www.telerik.com/forums/filtering-html-characters

Currently, when kendo grid is initialized from an  already populated html table, there is then no way to freeze columns as there is no datasource specified in kendo grid initialization.

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.

When scrolling is disabled for a grid and column resizing is enabled, resizing a column acts in a strange manner and attempts to size all columns of the grid.  I would expect that only the two columns on each side of the resize handle should have their widths altered.  Otherwise scenarios can occur where you are completely unable to resize columns.  If this would not be default functionality, I would at least suggest a flag to enable it at grid setup.

global option for grid colums that sets the decimal scale of number editor ui

see https://www.telerik.com/account/support-tickets/view-ticket?threadid=1101276 for more details

We are using kendo Datagrid where we wanted to apply pagination.

We are using pageSizes property of pageable object to set the no of items per page to render. We are also using buttonCount property to control the number of buttons.

Problem : For example I have 200 records , if I set pagesSizes=1 so technically I will have 200 paging button and if i set buttonCount to 60 than UI gets distorted. Find below is stackblitz URL where I have set pagesSizes=1 and if you set Maximum number of buttons = 70 UI will break.

URL : https://cuezkg--run.stackblitz.io/ 

The grid validation does not work well when the grid is part of a complex form containing simple fields and a Kendo Validator.  See this forum thread: http://www.telerik.com/forums/grid-custom-validation-not-shown

The grid validation should integrate better with a form level kendo validator so you can validate both the grid and the simple fields easily.

Based on this demo: http://demos.telerik.com/kendo-ui/grid/pdf-export
Given a similar grid with more data, especially with whole phone numbers and text content which consist of a single large word with no spaces or line breaks.
When using Edge, it will squeeze and render the text unreadable, instead of wrapping the large word.
This issue doesn't occur on Chrome, it handles the wrapping just fine.
This happens when there are many columns, which causes each column to be given less space than needed.