I think the issue lies in the Filter.cs
file and the way the dates are serialised. There is a thread in Stack Overflow addressing the same error that may be a good starting point:
As one of our DevCraft Complete clients, you may take advantage of the way that the data is filtered and parsed server-side with the Kendo.Mvc.Extensions
namespace, which is part of the Kendo.Mvc.dll
namespace provides the DataSourceRequest
object. The DataSourceRequest
object needs to be decorated with the [DataSourceRequest] attribute to transport the Kendo UI Grid request information to the server in the correct format. Using this approach the data is returned to the Kendo UI Grid as correctly parsed JSON (grouped, filtered and sorted).
Instead of public async Task<Kendo.DynamicLinq.DataSourceResult> Handle(Query query)
use an ActionResult in combination with DаtaSourceRequest/ToDataSourceResult. The server controller will look similar to the code below:
public ActionResult Handle([DataSourceRequest] DataSourceRequest request)
ordenes = _dbContext.OrdenesDist
More information on using the ToDataSourceResult() extension method is avaialble in the following article:
Please have in mind that Kendo.DynamicLinq
is an open source project, and it is supported only by the community.
The Kendo UI Team will support you in finding the best solution for your scenario, however, if you wish to handle the server-side without the use of the Kendo.Mvc.Extensions
, I can only guide you as far as the Kendo UI Grid request format is concerned as well as the server response format needed for the Kendo UI Grid binding to work.
Finally, if you decide to keep the Kendo.DynamicLinq
, I would recommend using the Kendo UI DataSource transport parameterMap
property to its full potential. The Kendo UI Data Source parameterMap
is executed before each request and can be used to modify the data in the format expected by the server. Documentation is available at:
Telerik by Progress