see Ticket ID: 981260

var dataSource = new kendo.data.DataSource({
      type: "odata-v4",       
  });

works correct, but if you just define parameterMap
the payload of parameters is not "odata-v4" it changes to old odata
with this:

var dataSource = new kendo.data.DataSource({
        type: "odata-v4",
        transport: {
            parameterMap: function(data)
            {
                return data;
            }
        }
});

This feels like I set dataType JSON for transport, and if I just define beforeSend in Ajax Request,
I suddenly becomes XML just by defining a overwrite function.

Datasource result support querying the entities with ef directly column names present in the class.There should be a way to filter the entities with lazy loading them and firing the filters on them ..like if the entity candidate contains the list of interviews the ,then the canidate.interviews should be passed in the filter and value and operator should be passed

It would be good user interaction when multiple node selection is implemented.It saves lot of rework

When you have multiple spreadsheet components on the same HTML page, allow them to cross reference each other, similar to the existing referencing capability across multiple tabs (like worksheets) but across completely separate objects (like workbooks) - of course they would need to be on the same page.

As it stands only during a read the aggregate are fetched from the server via the dataSource. This is incomplete behavior. A grid should, if requested by the programmer,  fetch the aggregates on each update of a row in the grid. That way the aggregates will always reflect the sum(), etc.. correctly.

"Currently the custom offline storage does not support asynchronous requests". I received this response from Kendo support is response to an issue we have using SQLite for on offline storage. When we try this with local storage or session storage, dataSource.fetch().then() resolves correctly Please implement with SQLite.

JSON data sources should be nested rather than having to define and parse flat data structures.

When using serverFiltering=true on a listview, if you type quickly 'abcd' the datasource.read is fired 4 consecutive times, making 4 consecutive server requests. There is no cap. 'abcd' can be typed within even 1 second, that will result in 4 server request per second. Now imagine 20 users at the same time typing to filter and each keystroke firing a server request is kind of an unnecessary overload.

Send filters even when the server filtering is disabled

As its documented on serverFiltering , data parameter contains filter property which follows this schema:

filter[logic]: and
filter[filters][0][field]: name
filter[filters][0][operator]: startswith
filter[filters][0][value]: Jane

When I set serverFiltering to false, data parameter doesn't contain any information about current filter. (See image attached in my first post)

And the only way I have to send the filter option in a different format is querying the DOM input element .

Shouldn't it work the same way? no matter whether filtering is set either client-side or server-side?

Currently we can only have the CRUD Operations on the remote data source. Atleast thats what it looks like. 

Is it possible to have more custom operations on Data source that can make remote calls. Or maybe there are and I am not aware of it. 

XML namespaces have a purpose and are extremely useful in maintaining data. The Kendo framework not supporting these is absolute insanity. I'm not interested in rewriting half of my data feeds to support a framework. 

If Kendo is intended to be "the world's most complete HTML 5 UI Framework," it should be supporting something as basic as this. If there's a valid reason why not to do so, I'd love to hear it.

FYI - There are several related requests that have been voted by 100s of users and marked as completed. However, this support is only at the surface and not complete.

We need all kendo components to consistently support binding to more than just primitive properties but at a minimum to models with Id (for reference) and labels (for display).

Many kendo components support this simple concept with 'dataTextField' and 'dataValue' field, but as soon as we try to customize something seemingly simple (for example multi-checkbox filters on grid columns) we are left with custom coding because at that point kendo falls back to only supporting simple arrays of strings etc.

Thanks.

Currently all "data*-template" options are limited to use ad #ID selector to pick the template script from the page.
This is problematic in big SPAs that have multiple pages dynamically loaded with possible collisions in IDs.
To avoid the hassle of mantaining unique ids across all pages (or having to dynamically generate ids) I therefore propose to allow for any jQuery selector in those options.

<script type="text/template" class="myAwesomeTemplate"></script>
<div data-bind="source: dataSource" data-template=".myAwesomeTemplate"></div>

To maintain retrocompatibility a first search with the "#" can be performed before executing the selector.

Since I am not very good with GitHub, here is the code that I did implement:

function parseOptions(element, options) {
    var result = {}, option, value, templateElement;
    for (option in options) {
        value = parseOption(element, option);
        if (value !== undefined) {
            if (templateRegExp.test(option)) {
                templateElement = null;
                if(!value) {
                    throw new Error("Missing template selector in option " + option);
                }
                try {
                    templateElement = $("#" + value);
                    if(!templateElement.length) {
                        templateElement = $(value).first();
                    }
                } catch (jQueryError) {
                    throw new Error("Invalid template selector " + value + " for option " + option);
                }
                if(!templateElement.length) {
                    throw new Error("Can't find a template with the specified " + value + " selector in option " + option);
                }
                value = kendo.template(templateElement.html());
            }
            result[option] = value;
        }
    }
    return result;
}

A single managed Ajax / Socket connection (can set for Ajax or Sockets or have it fall back) that you can pass a model to on the client and a command CRUD (Get, Post, Put, Delete) and an ASP.NET WEB API implementation on server side in Web API / Socket.

The issue I encounter with DataSources is that you have to set up a connection test it and for every one its more work and testing and possibility of error  in the app. I just want a client side connection to Sockets or Web API that I can tell to save something and have to set up and configure this connection once in JS and onece in C#

If you pass the Universal Data Source Data Bus a Model a Command (Get, Post, Put, Delete) and a Name / Path for the Model it hits a universal service that processes this it generates a predictable Web API call pattern that Web API can easily be set up to (Controllers to meet) or one big controller

We have a MVVM object with a change handler.

One of the public properties on this MVVM object is a datasource.

This datasource has some default aggregate configuration, but some aggregate configuration is added later. (see first screenshot)

However, when the dataSource.aggregate(..) method is called the MVVM's change handler fires (see second screenshot). This is ok, but there is nothing to distinguish that the change handler has been fired ONLY because the aggregate configuration has changed. When run some code when the datasource is defined or loaded, but we don't want to run the same code when the aggregates changes.

Vice-versa someone might want to run just a smaller piece of code when the aggregate config changes.

Can the event that gets fired to the mvvm change binding have an e.action = 'aggregate' or similar?

When retrieving data from a remote datasource with a fetchxml via soap that include link entites you get objects that have property names that contain dots like "account.accountid" for example. That doesn't work with Kendo Grid for example. Kendo always tries to go one level deeper if the property name contains a dot. Hence you always have to parse/refactor the results of a retrieve.

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

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.

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.