Bug report

Filterable configuration in ForeignKey is not serialized in TagHelper Grid.

Reproduction of the problem

Open this REPL example

Current behavior

Filterable configuration in ForeignKey is not serialized in TagHelper Grid.

Expected/desired behavior

Filterable configuration in ForeignKey should be serialized in TagHelper Grid.

TicketID:

1692361

Environment

• Kendo UI version: 2025.2.702
• Browser: [all]

### Bug report

When using the default column checkbox filter menu and the data requested from the server takes time to load, the filter menu popup does not resize correctly when opening the menu for the first time.

The issue started to occur in version 2025.1.211.

### Reproduction of the problem

1) Enable the checkbox filter menu of a specified column. The Grid binds to remote data and the data operations are perfomed on the server.

2) Open the filter menu when the Grid is loaded.

3) The Read request triggers and a loader is displayed to indicate that the data is loading:

4) The options are loaded, but the popup container does not expand as expected:

5) Close the filter menu and opend it again:

### Expected/desired behavior

The filter menu popup must display all options when the data is loaded.

### Workaround

<style>
     .k-animation-container-shown {
        overflow: visible !important;
    }
</style>

### Environment

* **Kendo UI version: 2025.2.520
* **jQuery version: 3.7.1
* **Browser: [all]

Bug report

The rowReorder event does not return the correct newIndex when dragging a row from a lower row index to a higher row index.

Reproduction of the problem

1. Run this dojo https://dojo.telerik.com/omyPpaZb
2. Drag Chai and drop after Chang. Note oldIndex is 0, newIndex is 2, which is unexpected as indices are 0-based

3. Re-run the dojo to start fresh and drag Chang and drop before Chai and the indices are correct - oldIndex: 1, newIndex: 0

Current behavior

The returned newIndex is incorrect.

Expected/desired behavior

The returned newIndex should be correct.

Environment

• Kendo UI version: 2025.2.520
• Browser: [all]

Hi,

I'm following this document to load data into the grid view control using local data binding.

https://demos.telerik.com/aspnet-core/grid/local-data-binding 

I'm not sure this is an issue or expected grid view behavior when using local data binding. If loader-type and no-records are added. What happens is when there are no records, the Skeleton is still displayed and the no-records template is not displayed (see the attached image)

<kendo-grid mobile="Disabled" name="Grid" loader-type="GridLoaderType.Skeleton">
 <columns>
 <column field="ProductName" title="Product Name">
 </column>
 <column field="UnitPrice" format="{0:C}" title="Unit Price" width="130">
 </column>
 <column field="UnitsInStock" title="Units In Stock" width="130">
 </column>
 <column field="Discontinued" title="Discontinued" width="130">
 </column>
 </columns>
 <datasource type="DataSourceTagHelperType.Ajax" page-size="20" server-operation="false" data="@Model">
 </datasource>
 <filterable enabled="true">
 </filterable>
 <scrollable enabled="true" />
 <pageable enabled="true">
 </pageable>
 <sortable enabled="true" />
<no-records template="string HTML template, automatically centered" />
</kendo-grid>

Thanks

Bob

Bug report

The Core Grid throws an exception when setting its toolbar template through the ClientTemplateId option. The issue is a regression introduced in version 2025.2.520.

Reproduction of the problem

1. Configure the toolbar of the Grid like this:

.ToolBar(toolbar => {
     toolbar.ClientTemplateId("myTemplate");
})

Current behavior

An exception is thrown:

NullReferenceException: Object reference not set to an instance of an object

Expected/desired behavior

The configuration works without throwing exceptions.

Wokraround

Use the alternative way of setting the toolbar template, on the Grid's root level:

@(Html.Kendo().Grid <MyModel>()
      .Name("grid")
      .ToolBarClientTemplateId("myTemplate")

Environment

• Kendo UI version: 2025.2.520
• Browser: [all]

### Bug report

When using the sort" and "filter" toolbar commands, the "sort" and "filter" events do not trigger.

### Reproduction of the problem

 A Dojo sample for reporduction: https://dojo.telerik.com/ySEQTSSS

### Expected/desired behavior

The "sort" and "filter" events must trigger when sorting and filterng the columsn through the respective toolbar commands.


### Environment

* **Kendo UI version: 2025.2.520
* **jQuery version: 3.7.1
* **Browser: [all]

### Bug report

The "Clear Sorting" and "Clear all filters" labels cannot be localized when using the "sort" and "filter" toolbar commands.

### Reproduction of the problem

A Dojo sample for reporduction: https://dojo.telerik.com/JHJGUaSH

### Expected/desired behavior

The "Clear Sorting" and "Clear all filters" messages should be exposed for localization.

### Environment

* **Kendo UI version: 2025.2.520
* **jQuery version: 3.7.1
* **Browser: [all]

### Bug report

When an Editor component in inline mode is set as an editor in an InCell editable Grid, the Grid cell does not enter edit mode on "click". The issue occurs since version 2023.1.314.

### Reproduction of the problem

1) Create an InCell editable Grid.

2) Set an Editor component in inline mode as an editor to a specified Grid column.

3) Try to edit the cell.

4) The cell flashes and does not enter edit mode.

A Dojo sample for reporduction: https://dojo.telerik.com/zQUvDQEq (check out the "ProductName" column)

### Expected/desired behavior

The Grid column that uses Editor component in inline mode must be editable.

### Environment

* **Kendo UI version: since 2023.1.314
* **jQuery version: 3.4.1
* **Browser: [all]

### Bug report

When opening the filter menu of a specified column through the classic ColumnMenu, the filter container is displayed with scrollbars when the dropdown of the filter operator is opened.

### Reproduction of the problem

1) Define a Grid and enable its classic ColumnMenu.

2) Open the filter menu of a specified column and then open the dropdown to select a filter operator.

3) The filter container has scrollbars. The "k-menu-popup" element has "overflow: auto";

Use the following demo to test the case and select the "classic" type for the ColumnMenu: https://demos.telerik.com/kendo-ui/grid/column-menu

The issue does not appear when using version 2024.4.1112.

### Expected/desired behavior

The filter menu container must not change its appearance when the dropdown opens.

### Workaround:

<style>
.k-menu-popup {
    overflow: visible !important;
}
</style>

Bug report

When ParseFormats is set in the DatePicker editor used in the Grid popup, the picker does not show the field value to which it is bound.

Reproduction of the problem

1. Add a DateOnly? field to the model:

public DateOnly? OrderDate { get; set; }

2. Bind a Grid column to the field.
3. Set the default value in the DataSource:

.Model(model =>
{
    model.Id(p => p.OrderID);
    model.Field(p => p.OrderDate).DefaultValue(new DateOnly());
})

4. Configure Popup editing in the Grid.
5. Add a DateOnly.cshtml editor in EditorTemplates:

@model DateOnly?

@(Html.Kendo().DatePickerFor(m => m).ParseFormats(new string[] { "MM/dd/yyyy" }).HtmlAttributes(new { title = Html.ViewContext.ViewData.TemplateInfo.GetFullHtmlFieldName("") }))

Current behavior

When editing a record. The value of the OrderDate field is not displayed in the DatePicker.
If you remove the ParseFormats option from the DatePicker, it shows the value as expected.

Expected/desired behavior

The field value should be displayed in the picker, even when ParseFormats is set.

Environment

• Kendo UI version: 2024.4.1112
• Browser: All

Bug report

The column format applied through the .Format() option is ignored, if the column is bound to a nullable DateOnly field.

Reproduction of the problem

1. Declare a nullable DateOnly field in the view model:

public DateOnly? PaymentDate { get; set; }

2. Bind a column to the field and set its format:

columns.Bound(p => p.PaymentDate).Title("Date").Format("{0:MM/dd/yyyy}").Width(160);

Current behavior

The specified format is ignored, e.g., the Grid shows 2025-01-21, instead of 01/21/2025

Expected/desired behavior

The specified column format is applied.

Environment

• Kendo UI version: 2024.4.1112
• Browser: [all ]

### Bug report

When the Grid is initialized in a hidden container (for example, in a non-selected tab of a TabStrip) and its initial data binding is disabled (autoBind: false), the pager information is not visible when the data is loaded afterward.

### Reproduction of the problem

1. Initialize a Grid into a non-selected tab of a TabStrip and set its autoBind option to "false".

2. Select the tab and check how the empty Grid is rendered.

3. Call the read() method of the Grid's DataSource in the browser console to request the data.

4. The data is loaded, but the pager information remains hidden.

A Dojo sample for reproduction: https://dojo.telerik.com/njVgBvza

### Expected/desired behavior

The pager information must be available when the data is loaded into the Grid.

### Environment

* **Kendo UI version: 2024.4.1112
* **jQuery version: 3.7.1
* **Browser: [all]

Bug report

Dynamic Grid produces a RunTimeException when the Filterable() configuration is enabled

Reproduction of the problem

1. Configure the dynamic Grid based on the following example.
2. Set the .Filterable() API configuration of the Grid.
3. Notice that the application throws a System.ArgumentNullException: Value cannot be null.

Example

@model System.Data.DataTable

@(Html.Kendo().Grid<dynamic>()
    .Name("gridItem")
    .Columns(columns =>
    {
        foreach (System.Data.DataColumn dcolumn in Model.Columns)
        {
            columns.Bound(dcolumn.ColumnName).Title(dcolumn.Caption);
        }
    })
     ...
    .Filterable()
)

The aforementioned declaration will work in the previous 2024.3.1015 version of the suite.

Current behavior

The Grid makes the application throw a runtime error.

Expected/desired behavior

The Grid makes the application should not throw a runtime error.

Environment

• Kendo UI version: 2024.4.1112
• Browser: [all]

Enhancement

Expose the sorts TagHelper for the Grid's column filter datasource taghelper

Overview

Currently, the Grid's Column Filter Datasource Taghelper exposes the following inner child TagHelpers.

Unlike its HtmlHelper counterpart which happens to expose the .Sort() API configuration. For example:

.Columns(columns =>
{
    columns.Bound(p => p.ShipName).Filterable(ftb =>
    {
        ftb.Multi(true);
        ftb.Search(true);
        ftb.CheckAll(true);
        ftb.DataSource(dataSource => dataSource
            .Custom()
            ...
            .Sort(sort =>
            {
                sort.Add("ShipName").Ascending();
            })
        );
    });
})

### Bug report

When the Grid is set up for OData-v4 binding, the columns that bind to DateOnly fields fail to filter. The date value in the filter expression contains the time portion and the following error is thrown:

"The binary operator GreaterThan is not defined for the types 'System.Nullable`1[System.DateOnly]' and 'System.Nullable`1[System.DateTimeOffset]'."

### Reproduction of the problem

1) Create a Grid that uses OData-v4 binding.

2) Bind a specified column to a DateOnly field.

3) Filter the column through the default column filter menu and open the browser DevTools to review the response of the request.

//Model
public DateOnly LastProdUpdate { get; set; }

//View
@(Html.Kendo().Grid<ProductViewModel>()
    .Name("grid")
     .Columns(columns =>
        {
            columns.Bound(p => p.LastProdUpdate).Format("{0:dd/MM/yyyy}");
        })
        ...
        .Filterable()
        .DataSource(dataSource => dataSource
        .Custom()
        .Type("odata-v4")
        .Transport(t =>
        {
            t.Read(read => read.Url("/odata/Products").Data("function() {return {'$expand': 'Employee'} }"));
        })
        .PageSize(10)
        .ServerPaging(true)
        .ServerFiltering(true)
        .ServerSorting(true)
     )
)

### Expected/desired behavior

The DateOnly fields must be filtered successfully as the DateTime fields.

### Environment

* **Kendo UI version: 2024.4.1112
* **Browser: [all]

Bug report

When the Grid is nested in a relatively positioned container, during the export the Grid gets an overflow style to its wrapping element. Then the style is removed and re-added again. This happens in a loop, which results in a vertical scrollbar constantly appearing and hiding.

Reproduction of the problem

1. Open this dojo example: https://dojo.telerik.com/IZoxOvOG/7
2. Click the "Export to PDF" button in the Grid's toolbar

Current behavior

Flickering caused by a scrollbar appearing and hiding

Expected/desired behavior

The Grid should remain unchanged during the export and no scrollbar should appear and hide during the export.

Environment

• Kendo UI version: 2024.3.806
• jQuery version: x.y
• Browser: [all ]

Bug report

Grid Hidden Column is set as exportable by default for Pdf and Excel

Reproduction of the problem

1. Set a Column as hidden through the Hidden() API configuration.
2. Add both the ToolBar.Excel() and ToolBar.Pdf() API configurations.
3. Notice, that the hidden column is exported.

Current behavior

The Grid Hidden Column should be set as exportable by default for Pdf and Excel.

Expected/desired behavior

The Grid Hidden Column should not be set as exportable by default for Pdf and Excel.

Environment

• Kendo UI version: 2024.3.806
• Browser: [all]