Last Updated: 17 Jun 2019 09:42 by ADMIN
### Bug report

Ticket ID 1410772

### Reproduction of the problem

Calling dataSource.query with an empty object before the grid is initialized throws an error.


          var dataSource = new{
            type: "odata",
            transport: {
              read: ""
            pageSize: 5


          var grid = $("#grid").kendoGrid({
            dataSource: dataSource,

### Current behavior

An error is thrown.

### Expected/desired behavior

No error should be thrown

### Environment

* **Kendo UI version:** 2019.2.514
* **jQuery version:** 1.12

Last Updated: 14 Jun 2019 11:32 by ADMIN
Created by: Raymond
Comments: 0
Category: Grid
Type: Feature Request
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

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.
Last Updated: 10 Jun 2019 09:58 by ADMIN

### Reproduction of the problem
1. Run the Checkbox selection demo in IE 11.706.17134 -
2. Try clicking a checkbox

### Current behavior
Two clicks are required to change the state of the checkbox.

### Expected/desired behavior
Checkbox should be checked/unchecked with a single click

### Environment

* **Kendo UI version:** 2019.2.514
* **Browser:** [ IE 11.706.17134 ] 
Last Updated: 04 Jun 2019 14:02 by ADMIN
Created by: Michael
Comments: 1
Category: Grid
Type: Feature Request
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, but there is no aira-label text to indicate the sorting behavior. 
Last Updated: 31 May 2019 15:01 by ADMIN

Cannot read property 'groupHeaderColumnTemplate' of undefined.

I have my grid, with 4 columns:


var dataSource = new{
                    transport: {
                        read: {
                            url: Utils.getUrlServices() + "getGrid",
                            dataType: "json",
                    requestEnd: function (e) {
                    schema: {
                        model: {
                            fields: {
                                id: {type: "number"},
                                name: { type: "string" },
                                    namecompany: { type: "string" },
                                hours: {type: "number"},
                                date: {type: "date"}
                    pageSize: 500,
                    group: [
                             field: 'name',
                             aggregates: [
                                          {field: "hours", aggregate: "sum" }
                         }, {
                             field: 'nomeImpresa',
                             aggregates: [
                                          {field: "hours", aggregate: "sum" }
                         { field: "hours",
                             aggregates: [
                                  {field: "hours", aggregate: "sum" },
                                  {field: "name", aggregate: "sum"},
                                  {field: "nameCompany", aggregate: "sum"},
                                  {field: 'date', aggregate: 'sum'}
                         {field: 'date',
                             aggregates: [
                                          {field: "hours", aggregate: "sum" }
                     aggregate: [
                         {field: 'hours',aggregate: 'sum'}
                self.Grid.set("source", dataSource);



When i grouping for Date field, the browser run this error: 


kendo.all.js:65435 Uncaught TypeError: Cannot read property 'groupHeaderColumnTemplate' of undefined
    at HTMLTableRowElement.<anonymous> (kendo.all.js:65435)
    at Function.each (jquery.min.js:2)
    at I.fn.init.each (jquery.min.js:2)
    at init._renderGroupRows (kendo.all.js:65417)
    at init.hideColumn (kendo.all.js:64983)
    at Function.KendoUtils.hideGridColumns (kendo.utils.js:330)
    at init.dataBound (eval at <anonymous> (jquery.min.js:2), <anonymous>:77:32)
    at d (jquery.min.js:2)
    at init.handlers.<computed> (kendo.all.js:9520)
    at init.trigger (kendo.all.js:124)










Pending Review
Last Updated: 28 May 2019 08:51 by ADMIN

After the kendoGrid is created, the headerAttributes field (of every column) has a id value (generated by Kendo) of some random GUID - but this GUID is nowhere to be found in the entire HTML.

So, there is no way to link a Kendo column object to an HTML (th) element.


Pending Review
Last Updated: 28 May 2019 07:42 by ADMIN
Whether you try to resize a "grouping column" (a column without an associated field) or a "data column" (the lowest level column - one with a data-index), resizeColumn does not work. The grid gets messed up. Sometimes the wrong column gets resized, sometimes columns just disappear. 
Last Updated: 23 May 2019 05:50 by ADMIN
Release 2019.R2.SP.Next

The issue is reproducible when the grid consists only from Multi-header columns, the setDataSource() method has been used and one of the columns is initially hidden.

After setting the new data source, the last header gets hidden. The "display: none;" style has been applied to the "th" HTML element.

Steps to reproduce:

1. Create a grid with multi-header columns only.

2. Hide one column initially.

3. Set a new data source via the setDataSource() method.

4. The last column gets hidden.

Sample Dojo:

Kendo UI version: 2019.1.220

Pending Review
Last Updated: 22 May 2019 07:06 by Harry Gozlan

When there is not enough space for the filter menu to be opened downwards, it should be opened on top. However, the first time it is opened, it is positioned below the filter button. 

Experienced behavior: 

Filter menu is mispositioned when first opened. With consequent openings, the menu is positioned as expected.

Expected behavior: 

The calculation for the positioning should be done even with the first initialization.

A sample Dojo for the reproduction of the issue:

First initialization:

Second opening:

Last Updated: 17 May 2019 12:44 by ADMIN

We need a way to disable the _step function (kendo.web.js) from being run whenever keying up or down in a nullable NumericTextBox grid column. Without this, moving between cells is setting the value of the cell being stepped out of to zero despite no text/numerical input. Our workaround was to override the Kendo JS to skip the majority of the _step logic by checking for whether spinners were disabled:

if(that.options.spinners === false) {


See support ticket logged for further information and code/video example:

Last Updated: 16 May 2019 17:05 by Tsvetina
It seems that you would want to conditionally have clearSelection() behave differently with persistSelection enabled, as it does not clear the selection of items on other pages. At the very least offer us a clearAllSelections() method if modifying the behavior of the other method is not desirable.
Last Updated: 09 May 2019 08:55 by ADMIN


The Kendo UI Grid has the ability to conditionally hide/show the command columns. But in order to hide some buttons from the toolbar, you need a dataBound handler. It will be useful to hide the "Create" button from non-admins, but be able to show the PDF and Excel Export or hide the entire toolbar.

toolbar: [
    { name: "create", visible:function(){ return isAdmin; } },
    { name: "reports" , visible: function(){ return isManager }},
    { name: "cancel" }

Currently, we need to use this dataBound handler:

 function onDataBound(e) {
   if (true) { // the condition against which you want to show/hide the toolbar
     this.element.find(".k-grid-toolbar").hide(); // hides the entire toolbar
     this.element.find(".k-grid-add").hide(); // hides just the Create button

Thank you in advance,

Pending Review
Last Updated: 07 May 2019 09:00 by ADMIN

Bug report


Reproduction of the problem

  1. Open the dojo
  2. Enter in Edit mode via the Edit button
  3. Navigate to the Update button via keyboard

Current behavior

Detail Template is toggled on Enter.

Expected/desired behavior

When the target is any of the Command Buttons, the Grid should hide/show the detail view.


  • Kendo UI version: 2019.1.220
  • Browser: all
Pending Review
Last Updated: 01 May 2019 10:01 by ADMIN
Created by: vladan strigo
Comments: 6
Category: Grid
Type: Feature Request
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.
Pending Review
Last Updated: 24 Apr 2019 12:29 by ADMIN


When endless scrolling and grouping is enabled on the KendoUI grid, collapsing large groups causes the grid to load ALL the hidden detail rows into the DOM.


This takes a very long time for the grid to do, as well it violates the whole point of a paging system. (ie I only want you to load X records at a time). Afterwards the performance of entire website (including the grid) will be very poor since potentially thousands of rows have been loaded into the grid and then immediately hidden. Additionally, these rows do not add any value to the user, since they are all hidden anyways.


When a category is collapsed, the grid should NOT add any new rows for that category to the DOM.


I have included a sample that demonstrates the performance issues.

In Development
Last Updated: 15 Apr 2019 17:37 by Ranadeep
Created by: Sean
Comments: 14
Category: Grid
Type: Feature Request
The ability to export a grid to excel has been a great addition, we would like the ability to export in CSV and XML also.
Last Updated: 12 Apr 2019 08:31 by ADMIN

We are working on enterprise product, which uses Progress Telerik jQuery KendoUI components extensively purchased by our Company. In which Kendo grid is used in many modules of our product.

Now a days we are working on Accessibility (i.e. keyboard and screen reader) as part of out-of-box feature of our product.

The grid has been made accessible so that it can be navigated using the keyboard arrow keys, once it receives focus via Tab Key in order of tab index or Alt + W short cut key. In turn, this has spawned up one issue in terms of keyboard operatibility. You can now tab into the grid, use arrow keys to navigate to the cell containing action buttons and then again tab to the button that you want to activate.

This is causing confusion in terms of use of the tab key. Ideally, the tab should take focus from one widget to another. That is the tab key should have taken focus into the grid and pressing it again should have navigated away from the grid. But because of the action buttons displayed within the grid for each record, that tab also navigates controls within the grid widget. This causes numerous press of the tab key just to traverse past the grid widget.

Now due to this, user needing to press the tab key multiple times is an accessibility issue.

Also while referring Grid control demo on , we found the same type of behavior when traversing through “Edit” and “Delete” buttons. One of the code snippet developed by us using can be referred on

It would be great if this issue is addressed with a good accessible way.


Please find below reply received from on the accessibility forum, when we tried raising the issue to find out the remedial solution:

Reply 1 by "Glen Walker"

Just to make sure we're talking about the right type of component, a grid vs a table, a grid is like a spreadsheet where you can interact with all the cells.  I agree that a grid should be a single tab stop so that you can easily navigate to the elements after the grid.  However, I have seen implementations that once you're in the grid and in "edit mode", you can tab amongst the cells.  This is helpful if the cell contains an element that uses the arrow keys (such as a radio or select) and you want the arrows interpreted by the element and not navigate to the next cell.  You then need to get out of "edit mode" (perhaps via the escape key) in order to tab off the grid.

A table, on the other hand, doesn't let you interact with the cell directly but that doesn't mean a cell cannot have an interactive element.  That is, you can have links or buttons or inputs in a table cell and it'd still be considered a table and not a grid.  It's kind of a fine nuance.  A grid lets you interact with the cell itself and a table might let you interact with an element that is in the cell, but not with the cell itself.

There is, of course, more to this than that but I was trying to keep it basic and simple.

So, that being said, do you really have a grid or a table?

Let's say you really have a table instead of a grid, and that one of the cells in your table has several buttons, and that pattern is repeated on every row.  You would indeed have a bunch of tab stops, making it difficult to navigate beyond the table.

One possibility is if all the button actions are grouped together, they could be considered a toolbar.  A toolbar is one tab stop and you arrow between the buttons, but you'd still have the problem of having a toolbar on every row.  A toolbar would reduce the number of tab stops compared to having all separate buttons but you'd still have X number of tab stops for X rows.  One for each toolbar.

Maybe a grid in that case would be better.  Tab to the grid, tab again to whatever element follows the grid.  Tab back to the grid and use the arrow keys to navigate to the desired row.  Maybe the row goes into "edit mode" automatically when it receives focus with the arrow and then all the interactive elements in the row get a tabindex of 0.

That might be a bit non-standard and there probably isn't a good "role" to explain the behavior.  A bit of usability testing might be required.



Chirag Vidani

Pending Review
Last Updated: 27 Mar 2019 05:36 by ADMIN
Created by: Karl Mikesell
Comments: 3
Category: Grid
Type: Feature Request

It would be nice if additional template variables where available, the only two: pageNum & totalPages are not enough.

Consider Time of Day & Filename at a minimum.


Last Updated: 20 Mar 2019 12:59 by ADMIN
Currently we use batch editing in the Grid control. The idea of batch editing is all changes are retained client side until the user presses the save button. 

When editing a cell a red dirty indicator is placed on the cell. This gives the user an indication that there are unsaved changes. however, when deleting a row, the row just goes away. There is no indication the user must still save. 

I would like to see rather than the record immediately removed a class applied to the row so we can apply some style like a strikethrough or red background color to indicate a pending delete. Also, we would be able to switch the "delete" button to an "undo" button.
Last Updated: 14 Mar 2019 10:46 by ADMIN

Hello guys,

I am stuck with this problem for some time now. Everything works well with mouse, I can drag and drop column into grouping header normally. But on touchscreens I can't drag it. I am interested if anyone has had this issue?

1 2 3 4 5 6