Make spreadsheet support virtual scrolling as the grid does in this example - https://demos.telerik.com/kendo-ui/grid/virtualization-remote-data

This allows handling of much larger datasets than other methods of data binding.

It would be great to implement the "has" operator for OData V4 enum filter scenarios.

See http://www.telerik.com/forums/datasource---odata-v4---enums-not-supported-yet

Regards,
Kasimier Buchcik

Currently Kendo MVVM only supports a very simple binding syntax, one view attribute can be bound to one model attribute. I'd like to have real javascript expressions or function calls in bindings to support more complex scenarios, e.g. you only want to show the "submit" button in a form when all fields have been completed.

KnockOutJS supports this: http://knockoutjs.com/documentation/visible-binding.html#note_using_functions_and_expressions_to_control_element_visibility

Add full support for syncing of changes made to the HierarchicalDataSource in a TreeView and Grid. Currently, sync() does not perform the correct sequence of CRUD operations that represent the changes made to the data source or control.

It should be possible to specify a validate() method on each viewmodel that gets triggered each time a new model value is .set(). In case of an unsuccessful validation an error event or binding could be triggered.

See this forum post for details: http://www.kendoui.com/forums/framework/mvvm/getting-access-to-array-index-while-binding-an-array-source.aspx

For easy using local arrays with kendo DataSource it would be good to have a functionallity to assign an array (kendo.obersvableHierarchy) without configure transport for CRUD operations.
When using Kendo MVVM it's easy then to define a grid the columns and field, and bind only the observable array as datasource.

And it would be great to have the possibility to assing depended arrays as field in an array that will be used as datasource for a grid or dropdown. Then we can assing the depended array of a selected dataitem to another control. So there is an need to have a special datatype like "dependedArray" and changes to this depended array has no effect to all ohter controls that where the viewmodel was bound.
Then we have more time to develope business logic. 

Currently when the add() method is called on a DataSource, if the id, as defined in the Model, is included, then the sync method is called, the data is not persisted to the _pristineData object, and neither the Create nor Update transports are called.  This has the effect of not persisting the data and so if the cancel button is pushed on an edit screen, the added object is mysteriously dropped.  

Please see my post on the kendo forums for a more detailed explanation including demos of the issue.  http://www.telerik.com/forums/if-id-is-provided-in-add()-sync-does-not-update-_pristinedata-and-create-update-are-not-invoked

I would suggest that anytime the add() method is used, it should be considered a 'new' record, or at least when the id provided does not match with any other id currently in the data array. If it matches a record in the data array, run the Update transport, otherwise, run the Create transport.  Simply including a value for the id should not remove the record from ever being persisted. 

http://odata.github.io/WebApi/#04-26-InOperator

OData v4 now supports the IN operator as a short hand for multiple or queries (as of http://docs.oasis-open.org/odata/new-in-odata/v4.01/cn01/new-in-odata-v4.01-cn01.html#_Toc485385090 ). This could help to change code such as:

var selectedStations = $("#cmbStations").data("kendoMultiSelect").dataItems();
            var stationIds = [];
            for (var i = 0; i < selectedStations.length; i++) {
                stationIds.push({
                    field: "StationId",
                    operator: "eq",
                    value: stationId
                });
            }
            dataSource.filter({
                logic: "or",
                filters: stationIds
            });

into a much cleaner:

var selectedStations = $("#cmbStations").data("kendoMultiSelect").dataItems();
            var stationIds = [];
            for (var i = 0; i < selectedStations.length; i++) {
                stationIds.push(selectedStations[i].StationId);
            }
            dataSource.filter({
                field: "StationId",
                operator: "in",
                value: stationId
            });

The DataSource schema must be given a total value in order to page correctly. However, DataSource expects this value to come from a response body field. In some cases, we must work with systems that return the total value as a custom field in the response header. We need a way to read custom response header values. 

Yes, the DataSource transport uses jQuery.ajax, so we can implement a custom complete function to read the response headers from the jqXHR. However, complete fires AFTER schema.total is set so it does no good.

This is more of a feature request...

If I want to refresh a datasource every 60 seconds, be it a grid, a dropdown, etc., I have to add a snippet of code something like this:

var interval = 60000;

         setInterval(function()

         {
             $("#my-grid").data("kendoGrid").dataSource.read();
         }, interval);

Yes, I realize this is trivial, but it would be nice if you could add an AutoRefresh function directly to the DataSource API that handled all of this under the covers.  Example:

Hi Team,

I would like to request the functionality to include data flags within the Kendo UI DataSource similar to the JQuery Data Tables.  They allow you return multiple flags and messages so long as you always name the display list the same name in the JSON.  I would rather not use Form Data.

Thank you!

It'd be terrific if there was built-in access to client-side data stores (e.g. IndexedDb).

Bug report

The dataSource filter configuration only accepts string as value.

Reproduction of the problem

1. Open the Dojo example - https://dojo.telerik.com/@martin.tabakov@progress.com/uVAgAYem
2. Open the MultiSelect.

Current behavior

An error is thrown and the MultiSelect does not open.

Expected/desired behavior

There should be no error and the MultiSelect should open.

Environment

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

I ran into this problem wherein I receive a 'Maximum stack size exceeded error' when I try to bind a collection with circular references  to kendo ui grids and data viz charts.  My Angular SPA is using breeze to fetch server-side entity models. As these are entity models, they do have circular references. I am also using the angular-kendo library for the directives.

Current fixes include manual removal of such entities from the collection. It would be great if the controls can handle such collections.

 It would go great batch syncing. And controls would redraw(refresh) just once when array of items is added. Not refreshing control and manipulating DOM(very slow) each time the item is added to datasource.
Example use case: scheduler month events copying...

https://developer.mozilla.org/en-US/docs/Web/API/Broadcast_Channel_API

Hi
I was just wondering if there was a message bus /Broadcast Channel component that was part of kendoUI.

I am thinking you could use your Observables or or something like the MVVM tooling.

just that the mozilla example does not work, it may be way out of date

thanks in advance

Doug

It would be nice to be able to specify in a datasource filter two fields and an operator for the sake of data reporting. For example, where "completed date" is greater than "promised date" or "Actual cost" is greater than "estimated cost."

This sort of thing can be accomplished by calculated fields; a filter of where "cost overage" is greater than 0. The down side of the calculated field approach is all comparisons need to be pre-defined. 

At the moment, the DataSource only uses one field for its ID property (if you enter several, then only one is used, apparently).  This doesn't reflect reality, in that in many cases (where one record is a child of another), the key field for a database table is a composite (from 2 or more fields).  
The existing situation causes problems in inline editing of the KendoUI grid, because default values need to be set for foreign key fields, but if these are set to a valid value, then spurious calls to the Inline_Create method occur because the DataSource treats the record as a new record when it is not.
In any case, allowing multiple fields would simply reflect reality.