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

CheckBox is not serialized correctly when declared in the Template component.

Reproduction of the problem

1. Open the following Telerik REPL.
2. Notice that the CheckBox component declared in the Template for the Discontinued field is not serialized correctly.

Current behavior

The CheckBox is not serialized correctly when declared in the Template component.

Expected/desired behavior

The CheckBox should be serialized correctly when declared in the Template component.

Environment

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

Bug report

Regression introduced with 2024.1.130. Likely related to: #7650

Workaround: remove "px" from the width values, e.g.,

width: "80"

Reproduction of the problem

1. Run this dojo: https://dojo.telerik.com/ulOPUJEW/2
2. Compare the behavior of the Grid with R3 2023 SP1: https://dojo.telerik.com/alahAneG/3

Current behavior

The columns ignore their width setting and each column has 1/3 of the Grid's width.

Expected/desired behavior

The columns widths are proportionate to the specified width values (as in R3 2023 SP1).

Environment

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

Grid row drag and drop capabilities enhancement request.

Currently, in order to drop a row from one Grid into another empty Grid, adding a placeholder row to the empty Grid with custom logic is required: https://demos.telerik.com/kendo-ui/grid/drag-drop

It would be nice to have a more robust drag and drop functionality that doesn't rely on custom logic to such an extent.

### Bug report

When adding a new record in an InCell editable Grid with enabled "autoSync" option, it is not rendered in the Grid.

### Reproduction of the problem

A Dojo sample for reproduction: https://dojo.telerik.com/@gdenchev/omotILiP

### Expected/desired behavior

The new record must be visible at the top of the Grid table when the Create operation completes.

The last working version is 2024.1.130.

### Environment

* **Kendo UI version: 2024.1.319
* **jQuery version: 3.7.0
* **Browser: [all]

I'm using the grid with a Status Bar Template and a button component in the template.

When trying to reference the button using the data() method it returns "undefined".

I've made small changed to the Grid's "selection Aggregates" demo to show the problem:

Sample

In the sample code, when selecting a cell in the top grid, the "T" button should be enabled but the line

returns undefined.

Bug report

Setting the Reoderable.Rows.ClickMoveClick() API configuration explicitly to false results in an error when using the HTML Helper wrappers.

Reproduction of the problem

1. Open the following Telerik REPL.
2. Set the Reoderable.Rows.ClickMoveClick() to false.
3. Notice the thrown client-side error.

Current behavior

Setting the Reoderable.Rows.ClickMoveClick() explicitly to false throws the following error:

Expected/desired behavior

Setting the Reoderable.Rows.ClickMoveClick() explicitly to false should not throw an error.

Environment

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

Overview

At this stage, the ToolBar.Custom() API configuration does not expose built-in configurations for adding a handler and partial view. E.g:

        @(Html.Kendo().Grid <TelerikAspNetCoreApp455.Models.OrderViewModel>()
            .Name("grid")
            .ToolBar(toolbar => {
                toolbar.Custom().Name("Test1").ClientTemplateHandler("someHandler");
                toolbar.Custom().Name("Test2").ClientTemplateView(Html.Partial("_Test2"))
            })
            ...
        )

Current behavior

The ToolBar.Custom() API configuration does not expose built-in configurations for adding a handler and partial view.

Expected/desired behavior

The ToolBar.Custom() API configuration should expose built-in configurations for adding a handler and partial view.

Environment

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

It would be convenient to have built-in MultiColumnComboBox editing for the Grid.

I was hoping the component would show the addresses formatted in columns (as per a fields list) and then return the address concatenated into a single to the grid field (e.g. from .DataTextField("FullAddress")).

Hi, is there a way to configure the grid so that when it's grouped and later sorted, the grouping state (expanded/collapsed) is preserved?

Kind Regards

Erwin

By default, when the "paste" command is added, the default option is "insert" mode ("Paste (Insert)"). Is it possible to add an option that allows setting the default paste mode to "replace" ("Paste (Replace)")?

Is it possible to implement template options for the "update" and "cancel" column commands of the Grid?

For example:

$("#grid").kendoGrid({
  columns: [{ 
    command: [{
        name: "edit",
        template: {
            update: "<button class='customUpdate'>Save</button>",
            cancel: "<button class='customCancel'>Cancel</button>",
          }
      }]
   }],
  ...
});

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

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

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]

Current configuration: server-side filtering

Desired behavior:

1. Grid searches are "anded" to any existing filters
2.  When the search box is cleared the pre-existing filters are retained

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 ]