IMHO it would be good to separate the DTOs and the serializer/deserializer into separate assembly packages and document the protocols used to communicate with telerik components as developers may create multi layered applications without having to deploy the full telerik package eg. in business logic layers or data access layers

If onerecord is saved in database and that record contains onw value which is saved using multiselect and that record will not removed updating that recordi

Add the options to open data source by pressing the "Down Arrow" in the keyboard in the next components: 
autoComplete/ dropDownList/ comboBox

As requested in this thread:
http://www.telerik.com/forums/filtering-support-for-pivotgrid-pivotdatasource

I think it would be extremely helpful to offer the same level of filtering on the PivotDataSource for a consistent development experience (especially since PivotDataSource 'inherits' from DataSource:
http://docs.telerik.com/kendo-ui/api/javascript/data/pivotdatasource).

Thanks!

For controls like ListView (web and mobile). We have features like server filtering. I feel there should be a configuration to perform filter operation mixing both client side and server side filtering. 
Scenario 1: Lets say I have 20 results to be populated based on the filter criteria and I have 2 results already present on the client side and rest 18 are present on the server rather than fetching all 20 results from server freshly this way data transfer can be optimized up to certain extent.

Scenario 2: filtering should results based on the client side results and list out 2 results and there should be option load more from server similar to outlook mail search feature.

It would be really useful to have an option on a data source to keep all data items when retrieving next page data. This feature would have been useful in https://github.com/telerik/kendo-mobile-music-store (where a workaround has been implemented, however this workaround does not work with groups)

Currently, an inherited DropDownList widget can only bind to another of the same type  or another vanilla DropDownList (via  alternativeNames array at kendo.all.js line 32813) 

A use case is that I originally created ParentCustomDDL and ChildCustomDDL with the intention of cascading from parent -> child. Since alternativeNames is hard-coded, I was forced to merge the code into one clumsy widget so that name matches name.

The success() function in the DataSource should check the response status. If the status is 304 "Not Modified", that indicates that the data has not changed and so the DataSource should not modify its internal data structures nor fire the "change" event.

There are several undocumented methods on the data source which provide some really nice functionality. The DataSource is able to store multiple 'pages' of data in an internal collections of ranges that can be accessed and populated by the range() and prefetch() methods. It looks like this is used mostly to support virtual grid scrolling, but I have found it very useful for other applications where a data source uses server operations. This is a really great feature and I'd like to see it officially supported in the future!

I need way to revert all changes for observable view model

Please consider creating a node.js middleware for mongoose so we can easily implement server side paging, filtering, etc for data source requests using node.js and mongoose (mongodb). Although mongodb itself is schema-less, mongoose does use schemas and is the most popular choice for working with mongodb and node.js. Currently, there is no other solution (that I am aware of) that offers similar functionality.

The only thing that currently comes close to providing such functionality is JayData which includes support for mongodb only in their pro edition and forces you to use it in place of mongoose and one would need to use oData to make everything work, essentially making it an undesirable solution for most.

PouchDB is a great way to both persist and sync data. It would be beneficial for DataSource to support PouchDB database, the way it currently supports SignalR and OData.
Here's PouchDB site: http://pouchdb.com

We need to bind RDF data to kendo controls. But we have a problem with some symbols in RDF standarted data format. Please, add support RDF data in kendo Observable object or create new type of observable data

<span data-format="dd MMM yyyy" data-bind="text: Created"></span>

Spits out (as text inside the span)...
   Fri Aug 01 2014 01:00:00 GMT+0100 (GMT Daylight Time)

Whereas ...
<input class="k-input" data-bind="value: Created" data-format="dd MMM yyyy" data-role="datepicker">

Spits out "01 Aug 2014" in the editable field.

Feedback from telerik: "span doesn't have data-format support".

Databinding telerik obervables to templates appears to be working in a completely different way to binding to telerik controls, this is confusing and causes a lot of frustration.

var model = { any js object };
var component = $("anything");
kendo.bind(component, model);

This should result in the same output no matter what model is (datasource, observable, flat js object).

Using: 
   $("selector").kendoControl({ options }); 

should behave the same as:  
<div id="myThing" data-bind=" options " />

kendo.bind($("myThing"), model);

We are using MVVM, a DataSource, and a Template to display a list of objects. We have a div rigged up with "source: vehicles", and the "vehicles" variable is a DataSource. We also rig up the DataSource with a Pager, so it doesn't display all vehicles at once. We default the DataSource to a PageSize of 20, then when a user reaches the bottom of the list, it automatically extends the PageSize by 10 (endless scrolling).

The problem with this is that every time the PageSize changes, it redraws every single item that is displayed. So when the PageSize reaches 100-ish and beyond, the browser begins to lag on every PageSize change, since it is redrawing every item every time.

We need an option for the PageSize change to recognize which items are already drawn and only add to the list the new items that need shown.

I'd like the formatted "text" property of the DatePicker widget to be bindable to a model. The DatePicker widget currently supports the value binding. 

This way the model would contain the same string value entered by a user and not a javascript date object.

Currently the grid fires the change event if the user clicks on a row. I can use this event to do something, for example, update controls in a detail part of the page below the grid.

If the user groups or sorts the grid, the grid rebinds. It does fire an event for that, but since the grid also removes any selection, to be consistent, it should also fire the same event it fires when the user selects a row. After all...the selection is changing (to nothing).

kendoui data source should support working with arrays or arrays rather than arrays of objects
this way the json being passed between the client and server can be much smaller (and network times reduced)

it will require positional information in order to get to each field instead of name
it will be especially important for grids

We use a DataSource with a custom transport and read method to filter some data on the server.

return new kendo.data.DataSource({
    pageSize: 10,
    serverPaging: true,
    serverSorting: true,
    serverFiltering: true,
    type: "json",
    sort: {
      field: "name",
      dir: "asc"
    },
    transport: {
      read: function (options) {}....

As the user types we issue a read request but it would be nice to have a way to cancel the last read request with a method call (ie. abortRequest() or abortReadRequest() ). We can implement a work around as shown here https://dojo.telerik.com/@Dimitar-Goshev/IxaLUtIw but I think it would be reasonable feature to simply have this internalized into the DataSource code so that the abort logic is internal to the DataSource class.

Currently, when binding an observable viewModel to a date/time picker control, only date formats built in to the widgets ( a minimal set) and formats specified implicitly by the ParseFormats option. 

I understand the reason for this being to prevent users from being able to type a date or time into the widgets in a format other that what is deemed appropriate for the widget, but it should behave differently when being bound from a view model.

Different platforms and web APIs serialize dates in different ways and developers should not have to always write a custom parser into the kendo datasource schema  for each datetime property of an object or have to specify the ParseFormat on the widget just so it can be bound properly to a date/time picker widget.

In the latest release (as of this posting) the parsing of Microsoft's JavaScriptSerializer date format has been added, ignoring the ParseFormats of the widgets. This is a great step in the right direction, however the W3C standard ISO 8601 date format is not being parsed while bypassing the ParseFormats of the widgets.

Also, currently, the date parser will not allow parsing of ISO 8601 date strings with more than 3 decimal places for fractions of a second. Both Microsofts DateTime.ToString("O") and Newtonsoft's Json.Net's ISO serialization of dates output 7 decimal places for fractions of a second. (I have been in contact with the kendo team about this specifically and they are going to add support, however they are not currently planning to make it bypass the parseformats unless the community votes for it here on UserVoice).

Since Kendo has specific functions used for binding widgets and elements, they should be able to easily make it so all parseformats (built-in and implicitly specified) are used when parsing dates that are set using binding to widgets expecting an actual date object and not a string (the date/time pickers).