Bug report

Kendo.Mvc.UI.GridBoundColum.SerializeValues throws an exception when using an Enum, decorated with FlagsAttribute.

This is a regression introduced with v2022.2.510. Possibly related to telerik/kendo@423e1e9

Reproduction of the problem

Using a ForeignKey column, bound to Enum, where the Enum has the FlagsAttribute throws an exception:

columns.ForeignKey(m => m.MyEnum, ....); // MyEnum is an enum with the FlagsAttribute

Expected/desired behavior

Using an Enum, decorated with FlagsAttribute should be possible, as in previous versions and an exception should not be thrown.

Environment

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

We noticed while testing the latest version (UI for ASP.NET Core R2 2022 (version 2022.2.510)) that hidden grid columns are incorrectly exported to Excel. Rolling back one version resolves the issue so it appears to be an issue in the new version.

I verified it in the grid demos on your site, and also verified that the bug is not present in the jQuery version.

jQuery version - no issue

1. Go to https://demos.telerik.com/kendo-ui/grid/excel-export
2. Click "Export To Excel" button - view the export
3. Use the columns menu to hide the Produce Name column
4. Click "Export To Excel" button - view the export and the Product Name column is correctly not exported

ASP.NET Core version - BUG

1. Go to https://demos.telerik.com/aspnet-core/grid/excel-export
2. Click "Export To Excel" button - view the export
3. Use the columns menu to hide the Produce Name column
4. Click "Export To Excel" button - view the export and the Product Name column is still exported but shouldn't be

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

### Bug report

When the filter is applied through the search panel, the query (more specifically, the filter expressions) is not built correctly. This results in displayed rows that have values that do not match the value from the search panel.

### Reproduction of the problem

1. Enable Search panel and group paging of the grid.

2. Set a value in the search panel and group by a column.

3. Expand the group and verify that there are items with values that do not match the filter expression from the search panel.

Short video demonstration:

https://screencast-o-matic.com/watch/crXFlXVI3i0

### Expected/desired behavior

The returned results should comply with the filter expression built from the Search panel.

### TicketID:
_1543306

### Additional notes and explanation

The Search panel builds the filter expression with the logic operator "or". While this is correct when the actual query is further built from the data source's internals (group function of the kendo.data.js file), the filter will be built with the "or" logic instead of "and". This query has to be restructured in order to send two filter objects with the "and" logic. The first filter object should contain all filter expressions built from the search panel with the "or" logic operator and the second filter object should contain an expression with the operator "eq", the field by which the group is built, and the value. The two filter objects should be combined with the "and" logic. 

### Environment

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

Bug report

When the Grid's Group Paging is enabled and its content is grouped, the Multicheckbox Filter doesn't filter the group data correctly.

Reproduction of the problem

1. Run this REPL Example.
2. Group by a column for example „City”
3. Filter the Country column for example „USA”
4. Check the result for a specific City group

Current behavior

The group shows rows that shouldn't be included when the column is filtered properly

Expected/desired behavior

The group should only show the filtered rows

TicketID:

1546090

Environment

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

Bug report

The Grid's Pager pageSize DropDown selected value is not shown properly in the Less Material theme

Reproduction of the problem

1. Run this Demo

Expected/desired behavior

The value of the DropDown should be shown as expected

Environment

• Kendo UI version: 2022.1.119
• 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 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 Switch is used as an Editor in InCell editing, clicking on it closes the edit mode.
This is a regression introduced with v 2022.1.119

Reproduction of the problem

Refer to ticket 1557280 for a runnable sample

Current behavior

1. Click on a cell in the Discontinued column to enter edit mode
2. Click on the Switch
3. The Grid exits the edit mode without changing the state
   screencast

Expected/desired behavior

State should be changed

Environment

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

### Bug report

The Kendo UI NumericTextBox is not rendered properly when it is added as a custom column filter through the "columns.filterable.ui" option.

### Reproduction of the problem

1. Use the "columns.filterable.ui" and define a JavaScript function which initializes a Kendo UI NumericTextBox;

2. Open the column filter menu and type in the input;

3. The entered value is not visible.

A Dojo sample for reproduction (filter column "Age"): https://dojo.telerik.com/OFuYawuC

### Expected/desired behavior

The NumericTextBox is wrapped in an additional "span" element with class "k-textbox". It should be removed.

### Environment

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

Bug report

Grid throws an error when the default behavior of the pdf export event is prevented.

Reproduction of the problem

1. Run this dojo
2. Click the "Export to PDF" button

Current behavior

Inspect the console tab and note the submitted error:

Expected/desired behavior

No error should be thrown

Environment

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

Hi

Just to let you know that the Demo for the Grid SignalR feature is showing an error.

(see screen dump attached)

Thanks
Darryl

At moment the "ForeignKey" method supports only predicates. Is it possible to implement a String overload (a screenshot is attached)?

Currently, the TagHelper Grid cannot bind to local DataSource as in the HtmlHelpers: https://demos.telerik.com/aspnet-core/grid/local-data-binding

Is it possible to implement it?

Hello,

When you add any kind of filter to the grid, he is wrapped inside span with class "k-filtercell". It would be very usefull to add HtmlAttributes to the html element. Last time i wanted to add class only on the filtercell so i can customize the ui to match our theme. The idea was to have expression for each filter type so i can create css only for the filters. Most of the expressions were ok, because they were wrapped inside Template. But in cases like enum i dont want template, i want only to add class to the filtercell, so i can change it. Its not ok for one types to do the changes with filter expression, for other types to make changes with column.HtmlAttributes(...).

If not HtmlAttributes, at least .Class(...).

Regards,

Dinko

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.