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.

When you configure a grid date-column with a custom format, the value configured in 'format' is parsed using JSON.parse. This requires the use of double quotes for both keys and values.

var a = "{0:dd/MMMM/yyyy}";    // example from docs
JSON.parse(a);    // SyntaxError: JSON.parse: expected property name or '}'

var b = '{"0":"dd-MM-yyyy"}';
JSON.parse(b);    // jey! 

However, if you use the latter, the generated template goes fubar with the message:

"Invalid template:' ... <td>${kendo.format("{"0":"dd-MM-yyyy"\}",theDataField)}</td> ... "

This makes sense when you look at the quote mismatch..

In you web site we used the Html.Kendo().Grid Helper to build our code for the grid.
When a user refresh the page we want to keep the context of the grid, meaning the same page size the same sort and the same page number.

When we build the grind using Html.Kendo().Grid Helper the only option that we can not set is the Page number (the page that is being display).

I see that using the javascript we can set the page

<script>
var dataSource = new kendo.data.DataSource({
  data: [
    { name: "Tea", category: "Beverages" },
    { name: "Coffee", category: "Beverages" },
    { name: "Ham", category: "Food" }
  ],
  // set the second page as the current page
  page: 2,
  pageSize: 2
});
dataSource.fetch(function(){
  var view = dataSource.view();
  console.log(view.length); // displays "1"
  console.log(view[0].name); // displays "Ham"
});
</script>

But why this option is not available using the MVC Helper

.DataSource(dataSource => dataSource 
.Ajax().PageSize(24) 
.ServerOperation(true) // Paging, sorting, filtering and grouping will be done client-side 
.Read(read => read.Url("/results/gethomes")) 

This will be a nice feature to have.
Thanks

It would be nice to have the possibility of using own template for the exported data, as some data may be obtained from own functions.
Something like this:
            columns: [
                {
                    field: "ProductName",
                    title: "Product Name",
                    aggregates: ["count"],
                    footerTemplate: "Total Count: #=count#",
                    groupFooterTemplate: "Count: #=count#"
                },
                {
                    field: "UnitPrice",
                    title: "Unit Price",
                    template: '<div style="text-align: right; font-weight: bold;">#= kendo.toString(UnitPrice, "n2") #</div>',
                    exportTemplate: '#= kendo.toString(UnitPrice, "n4") #',
                    aggregates: ["sum"]
                }
            ]

Current filter control for a date column only shows a date picker, if the data that's bound to the column also contains the time part then the filters don't work properly. Adding a date time picker would solve the problem.

We want events for expand/collapse groups in Grid, similar to the existing events for details.
This events will helps us for personalize some funcionalitys.

Thanks.

Hello,

from our development I could collect some suggestions for improvement, which we would be pleased about in the future:

MVC
-> Grid
-> Export to Excel
- Do not show columns in export - currently only possible with Javascript
- Display additional columns in the export that are only displayed in the export and not in the interface 

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.

Currently, the Kendo grid has an option to apply only one type of filtering for a specific column (be it standard filtering or multi-checkbox filtering). 

There is a custom approach which actually builds a custom check box list that is attached to the standard filter. But, there are lot of options that are missing like Select All, Search box etc.

There should be a way where user can apply different types of filter criteria on the same column.

We now have operators that support filtering for null/empty values in grid columns.  These are available using the standard Filter Menu, which provides input fields and the operator dropdown list.  Our users really love the Multi Checkbox filtering, which allows them to choose any number of possible values at the same time.  The missing feature is that the Multi Checkbox filtering prevents us from finding the "empty" rows.

Much the same way that "Select All" is automatically added to the list of checkboxes, please add some sort of "null/empty" item to the list.  It would be great if this was configurable.  In some of our columns, it's not possible to have empty values, so it doesn't make sense to include the "empty" checkbox for those columns.

Be sure to handle scenarios when the data source is automatic based on the data in the grid and when a separate, custom data source is provided for the column.

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,
        };

When using the Nova theme locked command columns are not styled correctly.   
In the following dojo one command column is locked and not styled while another command column is not locked but styled correctly.
https://dojo.telerik.com/eWECAZEw

Here's the code in case the dojo doesn't work:

<!DOCTYPE html>
<html>
<head>
    <meta charset="utf-8"/>
    <title>Kendo UI Snippet</title>

    <link rel="stylesheet" href="https://kendo.cdn.telerik.com/2019.2.619/styles/kendo.common.min.css">
    <link rel="stylesheet" href="https://kendo.cdn.telerik.com/2019.2.619/styles/kendo.rtl.min.css">
    <link rel="stylesheet" href="https://kendo.cdn.telerik.com/2019.2.619/styles/kendo.nova.min.css"/>
    <link rel="stylesheet" href="https://kendo.cdn.telerik.com/2019.2.619/styles/kendo.mobile.all.min.css">

    <script src="https://code.jquery.com/jquery-1.12.3.min.js"></script>
    <script src="https://kendo.cdn.telerik.com/2019.2.619/js/kendo.all.min.js"></script>
</head>
<body>
  
<div id="grid"></div>
<script>
  var dataSource = new kendo.data.DataSource({
    data: [
      { category: "category 1", subCategory: "sub. category 1", name: "product 1", val: 1 },
      { category: "category 1", subCategory: "sub. category 1", name: "product 2", val: 1 },
      { category: "category 1", subCategory: "sub. category 1", name: "product 3", val: 1 },
      { category: "category 1", subCategory: "sub. category 1", name: "product 4", val: 1 },
      { category: "category 1", subCategory: "sub. category 2", name: "product 5", val: 1 },
      { category: "category 1", subCategory: "sub. category 2", name: "product 6", val: 1 },
      { category: "category 1", subCategory: "sub. category 2", name: "product 7", val: 1 },
      { category: "category 1", subCategory: "sub. category 2", name: "product 8", val: 1 },
      { category: "category 1", subCategory: "sub. category 3", name: "product 9", val: 1 },
      { category: "category 1", subCategory: "sub. category 3", name: "product 10", val: 1 },
      { category: "category 1", subCategory: "sub. category 3", name: "product 11", val: 1 },
      { category: "category 1", subCategory: "sub. category 3", name: "product 12", val: 1 },
    ]
  });
  
$("#grid").kendoGrid({
  columns: [
    { command: "edit", locked: true, width: 150 }, // <<-- columns is locked
    { field: "category", locked: true, width: 150 }, // <<-- columns is locked
    { command: "edit", width: 150 },
    { field: "subCategory", width: 200 },
    { field: "name", width: 500 }
  ],
  dataSource: dataSource,
  scrollable: true,
  selectable: "row"
});
</script>
</body>
</html>

Bug report

Regression introduced in R3 2019 SP1. Reproducible with the LESS themes.

Reproduction of the problem

Dojo example.

1. Open a column filter menu and click on one of the dropdowns in it.

Current behavior

All of the text in the filter menu gets selected.

Expected/desired behavior

No text selection.

Environment

• Kendo UI version: 2019.3.1023
• jQuery version: x.y
• Browser: [Chrome 77 | Firefox 69 ]

I hope other developers realize the importance of this feature and vote for it.

It would be nice (in fact, important to have) an event that we can hook into, after the Edit event fires but before the editor template (more relevant when the editor is a custom popup template).

Let me explain.  On my custom editor template, I have a few dropdownlists that are not defined as foreign keys from the grid datasource.  The dropdowns are defined on the template, usually with a Read action on it.  This read action fires when the template is rendered.  In the Edit event, I need to set some of the elements as different or hidden or shown based on the selected value from more than one dropdown.  This is needed so that some other elements are shown/hidden when the popup is rendered.  The problem is, The edit event is too early to know the selected items in these dropdowns since the data for these ddls are not loaded yet.  Since I need values from multiple dropdowns, hooking into individual databound events of the ddls won't work either.

So, if we had an event something like "BeforeRender" on the grid that fires after all the datasources are loaded and databound for all relevant elements on the editor template, but before the template is rendered onscreen that would be great.  Then, we can hook into this event and when we do, all the datasources for all the dropdowns, comboboxes etc. are loaded and databound already. We can use the items from these elements to show/hide other elements.

Hallo,

i have a grid with a lot of data for a better representation i show some related values with a template in the cell below each other. 
This solution is not optimal because I don't have the filter and sort function in the column header for every single field. 
Enclosed an example https://www.igniteui.com/grid/multi-row-layout which illustrates my wish.
I would be happy if you implement this feature in a future release.

Hi,

We are using Fusion software and the grid ARIA attributes of rows are "aria-describedby". This results in the invalid/wrong action tips for Fusion users. If we change it to "aria-labelledby" it works well. 

Currently, we have to override the private method _tmpl so we can edit the hardcoded attribute. We need to be able to change this part of the source:

It would be great if we can configure them from the grid settings.

Then the _tmpl function will change like this:


Thank you in advance.

Adding the same functionality as filterable.extra but in row mode. Similar to the following demo http://dojo.telerik.com/AkaYi/2.

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.

https://docs.telerik.com/kendo-ui/api/javascript/ui/grid/configuration/pdf.template

 

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.

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:

https://dojo.telerik.com/iRaDakEs

First initialization:

https://www.screencast.com/t/vmnVGhDBobi

Second opening:

https://www.screencast.com/t/S6Qzza6ve4UO