I have a Site http://www.amb-selfiesquaregurgaon.com/ . Can i track its page views,browsing time and any other statistical methods on this..can you please suggest me how can i achieve my goal.

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

how to bind remote data to the panel bar?

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

Hello,

 I knew there was "set" function for kendo.data.ObservableObject, it could change value of specified field.

But after this action, we need call "sync" method for data source manually, and sync action will fire some events/ data bound again.

Is there another method, that we only hope sync value of specified field, without fire events and data bound again?

Thank you.

It is possible to retrieve IEnumerable collection from DataSourceResult, but there is no option to get IQueryable collection that has not been evaluated. I think it might be helpful to use filters from grid that can be used to generate a query.

In order to clearly identify if a datasource operation is successful, 
two alternatives are possible:

1. Add success event to the datasource in order to get datasource operations separated from update, destroy, add. 

2. Enhance change event by error array. 
Currently, the change even is fired even in case of an error. So, at least an error array containing error messages should be available, together with a property "hasErrors".

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.

It would be really useful to be able to modify request parameters in the RequestStart event of the dataSource; this would be consistent with the functionality of the Kendo Tooltip RequestStart Event.

The filter row is really nice, but for more flexibility it'd be nice to not hit the server until a user has populated the row with all the filters they want. The way it works now is if you tab out/hit enter/select dropdown list item/etc. it hits the server. The ability to filter when the user explicitly wants to isn't really there.

Add Event handlers after Batch Edit, Save Changes

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?

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

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

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.

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.