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.

I'm currently evaluating the ASP .Net Core Components and whilst I'm liking it so far, I have to say - the documentation leaves a lot to be desired.

At the moment, I am trying to use grid and looking at documentation, I have no idea if I am meant to be looking in Kendo.Mvc.UI.Fluent or Kendo.Mvc.UI - and when I am there and find an item, there just isn't enough detail. In addition, the demos section appears to actually be more helpful and I'm constantly looking there.

What caused me to write this is that I have simply enabled GridFilterMode.Row on an instance and whilst I like it, I want to change the default from "Is Equal To" to "Contains"... I have been experimenting for the past few hours without any luck and I'm going round in circles on documentation:

I can see that Filterable requires GridFilterMode, but the documentation is lacking - https://docs.telerik.com/aspnet-core/api/Kendo.Mvc.UI/GridFilterMode#kendomvcuigridfiltermode

I then try to find the filterable modes documentation, but, half the features/methods just don't seem to have any affect whatsoever.

Personally, I'm having great luck learning about your components from the demo section and adapting the code to suite my needs - but, if there isn't a demo, it appears to be a very hard task to learn what is and isn't possible.

Per the documentation for the Grid's Search Panel:

"When the server operations are enabled, you can search only by using string fields."

This is an oddly-specific limitation to have that causes an awkward user experience. Grids in some areas with limited data might use client operations and, as a result, the Search Panel is capable of searching all columns in a Grid. Other areas, however, might have grids with significantly more data and be using server operations for performance reasons. A side-effect of this would mean the Search Panel is incapable of filtering on non-string fields. This not only might lead to unexpected results to an end-user, but also requires the developer to explicitly list each string field that can be searched. If a developer forgets to list only string fields, the default action will be for it to attempt to filter on all fields. If any fields happen to not be strings, you still get a loading indicator as if it's attempting to filter, but the Ajax request silently fails and returns an error 500 behind the scenes.

There are some manual workarounds discussed here, as well as some information as to why this limitation exists. It seems like the problems causing these limitations are known, as are some rough workarounds to get around it. It would be great if we could get some official support to address this limitation so developers aren't left to either work around it on their own or avoid using this feature altogether. This feature would be great if it weren't for this limitation. A single place to quickly and easily type in something to filter on, and have that filter applied against all columns could definitely save some time and be very useful, but with this limitation with a pretty technical explanation (from an end-user perspective), the unexpected mixed results could instead lead to confusion and frustration, and distrust of this feature.

Bug report

The DataSource's property groupPaging: true prevents the Grid's group from expanding if it has a defined groupHeaderColumnTemplate.

Reproduction of the problem

1. Open this Dojo
2. Try to expand the Grid's groups

Also reproducible in the Core wrapper where an error is thrown: kendo.all.js:8743 Uncaught TypeError: Cannot read property 'hasSubgroups' of undefined

Current behavior

groupPaging is not compatible with the groupHeaderColumnTemplate

Expected/desired behavior

groupPaging and the groupHeaderColumnTemplate should be compatible

Environment

• Kendo UI version: 2021.2.616

• Browser: [all]

IgnoreCase property is missing for the filterable options of the column:

https://docs.telerik.com/aspnet-core/api/Kendo.Mvc.UI.Fluent/GridBoundColumnFilterableBuilder

The option is documented in:

https://docs.telerik.com/kendo-ui/api/javascript/ui/grid/configuration/columns.filterable.ignorecase

Currently, the functionality for creating a toolbar template with TagHelpers is not available. 

Bug report

The Kendo UI Grid's pager for UI for ASP.NET Core does not have an "All" option and it can't be configured in the Razor syntax.

Current behavior

Using the Kendo UI Grid's pageable.PageSizes, the ALL option is not available for UI for ASP.NET Core as it's only an Int32[].

Expected/desired behavior

The All option should be included like in the UI for ASP.NET MVC Razor Syntax.

Environment

• Kendo UI version: 2020.3.915
• Browser: all

### Bug report

When a specified gird column has a property '.EditorTemplateName("Date")', the default DatePicker editor is not rendered properly.

### Reproduction of the problem

1. Create a new Telerik ASP.NET Core MVC Application by using the "Create New Project Wizard". Use the "Grid and Menu" Template;

2. Make the Grid "InLine" editable;

3. Set the property '.EditorTemplateName("Date")' to the "OrderDate" grid column;

4. Run the application and try to edit an existing record. The DatePicker editor is not displayed as expected.

Attached is a runnable sample for reproduction.

### Expected/desired behavior

The closing bracket in the DatePicker configuration should be moved at the end:

//Current configuration
@model DateTime?

@(Html.Kendo().DatePickerFor(m => m)).HtmlAttributes(new { title = Html.ViewContext.ViewData.TemplateInfo.GetFullHtmlFieldName("")})

//Updated configuration
@model DateTime?

@(Html.Kendo().DatePickerFor(m => m).HtmlAttributes(new { title = Html.ViewContext.ViewData.TemplateInfo.GetFullHtmlFieldName("")}))

### Environment

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

Bug report

When a hidden column of the Grid is configured as .Exportable(true) in the wrappers the exportable property doesn't get serialized

Reproduction of the problem

1. Use the following configuration
   columns.Bound(p => p.OrderID).Exportable(export=>export.Excel(true)).Hidden().Filterable(false);
2. Inspect the client-side script of the Grid

Expected/desired behavior

Setting the Exportable(true) on a hidden column should correctly include it in the export

TicketID:

1559232

Environment

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

### Bug report

When the Grid group paging is enabled, and the Grid is grouped, when the user search through the built-in search panel, and expand a specified group, an infinite loop appears. The Grid sends Read requests, and the server returns empty "data" property.

### Reproduction of the problem

1) Create a Grid bound to remote data and enable the group paging feature.

2) Group the Grid by a specified column.

3) Enter a value in the Grid search panel (the grouped data is filtered).

4) Expand a specified group --> it causes an infinite loop.

5) Open the browser Network tab to review the Read requests.

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

### Expected/desired behavior

The grouped Grid data should be filtered through the search panel as expected.

### Environment

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

Hi Kendo Team,

I am working on Kendo UI ASP.NET Core Grid binding with SignalR. But while starting Hub and providing the Promise, I am facing an error "The "promise" option must be a Promise."

I am following this URL for reference: https://demos.telerik.com/aspnet-core/grid/signalr .

Checked on your website as well, but the issue is also coming there. Here is the URL: https://docs.telerik.com/kendo-ui/api/javascript/data/datasource/configuration/transport.signalr

In this link, when clicking on "Open In Dojo" button, it opens a new window, then clicks on the Run button. It will generate an error in the console "Uncaught Error: The "promise" option must be a Promise.". 

Please check the attached snapshot.

Please reply asap. Thanks in advance!

Bug report

When the data source of the grid is set to WebAPI, the Batch option is not available. 

Reproduction of the problem

1. Set the DataSource to WebAPI()

2. Attempt to enable the Batch(true) option.

Description

Reproducible only with the latest version of the suite - 2019.3.1023. The Batch option is available in the 2019.3.917 version.

Environment

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

Bug report

The TagHelper Grid's TagHelper is not correctly serialized and cannot be used to export hidden columns.

Reproduction of the problem

• Set the exportable TagHelper for a hidden column to enabled.

<columns>
    <column field="Discontinued" hidden="true">
         <exportable enabled="true" />
    </column>
</columns>			  

• Open the following REPL example.
• Export the Grid and observe the exported document.

Current behavior

The Grid TagHelper does not export hidden columns if the exportable TagHelper is enabled identically to the Kendo UI for jQuery Grid column exportable option.

Expected/desired behavior

The Grid TagHelper should be able to export hidden columns if the exportable TagHelper is enabled identically to the Kendo UI for jQuery Grid column exportable option.

Environment

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

Bug report

When tabbing in a batch editable Grid cells do not enter edit mode.
This is a regression introduced with v 2023.2.606.

Reproduction of the problem

1. Run this dojo
2. Click on a cell in Product Name column - an editor is generated
3. Press the Tab key

Current behavior

The corresponding Unit Price is focused, but an editor is not generated

Expected/desired behavior

The cell should enter edit mode, as with v2023.1.425 - dojo

Environment

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

Overview

Currently, the ASP.NET Core Grid Columns's Template() method does not expose the ability to provide a delegate. In comparison to the ASP.NET MVC Grid Column's Template() method:

It would be useful to add this option to the ASP.NET Core Grid, as it will allow the configuration for multiline templates. For example:

.Columns(columns =>
{
    columns.Template(@<text>
        <div>#= OrderID # </div>
         <div>#= Discontinued # </div>
    </text>);
})

Current behavior

The Columns.Template() method of the Grid does expose a delegate overload.

Expected/desired behavior

The Columns.Template() method of the Grid should expose a delegate overload.

Environment

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

Bug report

There is an edge case in the Pager's responsive configuration. If the width is between 480 and 600 pixels both the DropDownList and Buttons that allow the user to navigate through the pages are hidden.

Reproduction of the problem

1. Open this Dojo
2. Resize the right pane to be between 480px and 600px
3. Run the Dojo

Current behavior

The buttons and dropdown are missing

Expected/desired behavior

The Pager should display a DropDownList for page selection when it is wide between 480 and 600px.

Environment

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

The Kendo UI Sortable for ASP.NET Core assumes that all selectors are by "id".

Reproduction of the problem

1. Set the .For() option of the Sortable widget to a class selector:

@(Html.Kendo().Sortable()
    .For(".k-grid table")
    // . . . 
)

2. Inspect the page source.

3. The following string is rendered:

<script>
    kendo.syncReady(function () { jQuery("\\.k-grid table").kendoSortable(// options) });
</script>

Expected/desired behavior

The Sortable widget should allow for passing any jQuery selectors.

Environment

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

Bug Report

Ticket ID:1486632

When using groupable.sort.compare with client operations and groupPaging, a JavaScript error is thrown:

Reproduction

Dojo

Environment

2020.3.915