Progress® Kendo UI® for jQuery Feedback Portal
Back to Feed
Request a Feature Report a Bug
Completed
Last Updated: 07 Jun 2018 13:45 by ADMIN
Christopher
Created on: 14 Jul 2015 19:45
Category: Data Source
Type: Feature Request
39
Add full support for oData v4
"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.
2 comments
ADMIN
Carl
Posted on: 07 Jun 2018 13:45 
With R2 2018 I believe that we can mark this item as completed! We've added batch support, as well as working with hierarchical data through the `$levels` query option. Since Web API OData 5.6 the DateTime type has been re-introduced, which means that we can use `$filter` and `$orberby` options across these data types along with the Kendo UI Grid which should resolve the issues we're dealing with in this feedback item.
Morten
Posted on: 20 Jul 2015 14:34 
This data source have a date field defined. This field is actually a DateTime in the backend. But filtering I only care about the date. So the type is set to date.

dataSource: {
    ...,
    type: "odata-v4",
    schema: {
        model: {
            fields: {
                LastChanged: { type: "date" }
            }
        }
    }
}

Using that in a Grid, for example. Would result in a datepicker filter which is working as intended.

However the generated query is incorrect as it compares date to datetime. Which breaks all filters with the equals operator.
The incorrect filter query: $filter=LastChanged eq 2015-06-29T00:00:00+00:00

It should have been: $filter=date(LastChanged) eq 2015-06-29

Please fix.
Create an account Log In
View
Type
Status
Category