Last Updated: 03 Jan 2020 15:15 by ADMIN
Created by: Patrick
Comments: 6
Category: Data Source
Type: Feature Request
At the moment, the DataSource only uses one field for its ID property (if you enter several, then only one is used, apparently).  This doesn't reflect reality, in that in many cases (where one record is a child of another), the key field for a database table is a composite (from 2 or more fields).  
The existing situation causes problems in inline editing of the KendoUI grid, because default values need to be set for foreign key fields, but if these are set to a valid value, then spurious calls to the Inline_Create method occur because the DataSource treats the record as a new record when it is not.
In any case, allowing multiple fields would simply reflect reality.
Last Updated: 02 Oct 2019 11:24 by ADMIN
Created by: SAM
Comments: 0
Category: Data Source
Type: Feature Request

When the grid is configured for working with UTC on the server-side, the value sent from the filter menu on the client-side would not be properly sent to the server. 

If the stringifyDates option of the transport of the data source is set, the value would still be sent in a localized date format without information for the time zone, for instance, GMT(+0300).

In case the value sent from the client is modified, the parameterMap would be called afterward and would override the modified value. 

Moreover, the Kendo UI Binder on the server-side is not configured to be working with dates that have additional data for the time zone appended to the end. Therefore, sending the modified data would not be parsed correctly and FormatException error would be thrown.

Last Updated: 29 Jul 2019 13:54 by ADMIN
Created by: Imported User
Comments: 2
Category: Data Source
Type: Feature Request
When using aggregates, it should be possible to define your own aggregate function, or even set it globally for kendo, so it could be used in other places. i.e. 

currently you can only specify the function name like 'sum', 'avg', etc. with this idea you could give the whole function like function(arguments...) {}

Also from what I saw it would be nice to have the `functions` object from accessible, so you could add your custom functions, like:
`['median'] = function(arguments...) {}`