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.

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;
}

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. 

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?

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

utfq8

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.

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:

           .DataSource(dataSource => dataSource
               .WebApi()
               .PageSize(20)
               .Model(model =>
               {
                   model.Id(m => m.StoreId);
               })
               .Read(read => read.Url(Url.HttpRouteUrl("GetData", null)).Data("additionalData"))
               .AutoRefresh(60) // seconds
               .Events(e => e.Error("onError"))
           )