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)?

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.

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

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

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] 

Hi folks!

I am using the Grid's ColumnMenu with its new ComponentType-property set to "modern" like this:

@(Html.Kendo().Grid<my_fancy_web_application.ViewModels.ProjectListViewModel>()

                .Name("myGrid")
                .Editable(editable => editable.Mode(GridEditMode.InLine).DisplayDeleteConfirmation("Willst Du diesen Eintrag wirklich löschen?"))
                .Sortable()
                .Scrollable()                
                .Pageable(pageable => pageable.Enabled(false))
                .ColumnMenu(columnMenu => columnMenu.ComponentType("modern"))
// ... going on with some further definitions
)

In the <head>-Tag of my _Layout.cshtml file, I have set the Kendo Culture to Swiss German:

<script>kendo.culture("de-CH")</script>

What I now observed is, that the buttons "Apply" and "Reset" did not get translated properly and remain in English (see Column_Menu_Reset_Apply_Button.png). Whereas other messages are correctly translated. 

I tried to find out which message property was set there, so that I could add it manually to the "kendo.messages.de-CH.min.js" (as by the way I still have to do for e.g. the Grid's searchbar placeholder "Search..."). 

In the loaded kendo.all.min.js (2021.1.330) I discovered, that there was no message property in place, and the texts were rather hard-coded:

'<div class="k-columnmenu-actions">' + '<button class="k-button" type="button">Reset</button>' + '<button class="k-button k-primary" type="button">Apply</button>' + '</div>' + '</div>'

With the Chrome's dev tools and the source map, I found the above code on line 55815 by searching for the class "k-columnmenu-actions".

Could you please change the mentioned code to make use of the kendo.messages-properties and update the culture-specific kendo.messages files accordingly?

Thanks in advance!

Kind regards,

Janick

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.

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

Bug Report:

Whenever the foreign key column of the grid is configured for multi checkbox filtering and is nullable, the value of the "null" option is sent to the server as "NaN".

Steps to replicate:

1. Set ForeignKey column

2. Make the column nullable

3. Set the filterable.multi option to true

4. filter by the null value

A sample project with reproduction has been shared in Ticket with ID: 1463089

Bug report

Grid's items are not correctly calculated when a group is expanded and groupPaging is set to "true".

Reproduction of the problem

1. Open this Dojo and run it
2. Expand the "Assistant Sales Agent" group.
3. Expand the "Assistant Sales Representative" group

Current behavior

On the expand of the "Assistant Sales Agent" group, the footer displays the following:

On the expand of the "Assistant Sales Representative" group, the footer displays:

The number of the displayed items is incorrectly calculated

Expected/desired behavior

The number of the displayed items should be calculated based on the number of the rows inside the opened groups

Environment

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

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] 

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