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.
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.
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.
In MDX you can sort the data you query for using the order function, specifying a set, a value to sort by (most commonly a measure) and the direction and whether to break hierarchy or not. I appreciate that hierarchy-breaking sorting might be quite difficult to pull off nicely, but I believe the MDX could be generated in such a way to support sorting, by specifying one of the members on an axis and the measure.
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.
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.
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".
Ignore language specific characters when filtering. Example: search phrase "Deja" should find word "Déjà".
"WebAPI now uses the DateTimeOffset time as a main type when it comes to dates. However DateTimeOffet requires the Model(that the dataSource creates) to keep information for both Date and Offset which is not possible with the current architecture of the DataSource and Model of Kendo." Based on http://docs.telerik.com/kendo-ui/aspnet-mvc/helpers/grid/how-to/oData-v4-web-api-controller Please add full support, also when working with Dates. Thanks.
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.
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!
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.
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.
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 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
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
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.