### 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

Reproduction of the problem

Dojo example: https://dojo.telerik.com/eRazIrIB

1. Scroll the Grid

Current behavior

The data is requested, but it is not displayed in the Grid.

Expected/desired behavior

The data is displayed, regardless of the type of loader used.

Environment

• Kendo UI version: 2022.3.913
• jQuery version: x.y
• 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

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 filter menu is customized with a DropDownList, the initial option defined by using the "index" property is not set.

### Reproduction of the problem

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

### Expected/desired behavior

The DropDownList should be initialized with an initially selected option.

### Environment

* **Kendo UI version: 2022.1.119
* **jQuery version: 1.12.4
* **Browser: [all]

Bug report

Reproduction of the problem

1. Open the following dojo.
2. Open the column menu.
3. Try to remove all columns through the checkboxes.

Current behavior

The last checkbox selection is not disabled and allows all the columns to be removed if the menu options for the command column are explicitly set to false:

Expected/desired behavior

The last checkbox selection should be disabled without allowing all the columns to be removed if the menu options for the command column are explicitly set to false:

The following dojo depicts the aforementioned behavior.

Environment

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

Trouble on iPad 6/7/8 with Safari.

Using grid with batch and incell edit mode.

Datepicker is not working. It just shows the text box to manually type in date.

Every once in a while the date picker pops up and stays for selection.

Sometimes I see the dat picker, but it goes away suddenly before being able to set a date.

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

When a Grid's row is reordered and then the changes are saved - a Destroy request is sent to the server for the dataItem of the reordered row. This happens even though no changes are applied to dataItem of the reordered row.

Reproduction of the problem

1. Run this Telerik REPL or this Dojo
2. Reorder a row
3. Open the browser's Network Tab
4. Click the Save Changes button

Expected/desired behavior

The Grid should request the reordered item to be perished from the backend.

Environment

• Kendo UI version: 2023.2.718

### 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

Expose additional API configurations for the Grid's ToolBar

Reproduction of the problem

As of recent releases, the Kendo UI Grid Toolbar has been substituted with the Kendo UI Toolbar. This change allows users to add the majority ToolBar.items API options apart from the built-in tools.

As noted within the Kendo UI for jQuery API documentation for the Grid's Toolbar:

"Apart from the built-in tools, the Grid fully exposes the ToolBar.items API. This way you can specify any custom tools in the widget using the components available in the ToolBar itself."

Current behavior

The inherited ToolBar.items API options are not available for the server-side Telerik UI Grid for ASP.NET Core and MVC wrappers as well.

Expected/desired behavior

It would be beneficial to the customers if the inherited ToolBar.items API options are available for the server-side Telerik UI Grid for ASP.NET Core and MVC wrappers as well.

Environment

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

Bug report

In a .NET 7 project when TagHelper Grid is configured and RuntimeCompilation is employed, starting from version 2023.2.606 an unhandled exception is thrown.

Reproduction of the problem

1. Create a .NET 7 project
2. Enable RuntimeCompilation
3. Install a 2023.3.606 or later version of Telerik UI for ASP.NET Core
4. Configure a TagHelper Grid

Current behavior

When run a runtime error occurs

Expected/desired behavior

TagHelper Grid should exhibit the same behavior as HtmlHelper ones.

Environment

• Kendo UI version: 2024.1.130
• 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]

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

When the Grid is grouped by a specified column, and this column has a "groupFooterTemplate" that contains aggregates from other fields, it cannot be exported to Excel. It throws a JavaScript exception.

### Reproduction of the problem

1) Group the Grid by the column "ProductName".

2) Export it to Excel through the built-in command "Export to Excel".

3) JS exception is thrown.

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

### Expected/desired behavior

The Excel export should work as expected when the Grid is grouped.

### Environment

* **Kendo UI version: 2022.2.802
* **jQuery version: 1.12.4
* **Browser: [all]