Hello,
I have a sortable grid that's bound to a kendo dataSource with the following transport configuration:
Everything works fine when I'm sorting a column in ascending/descending order, but when I click on the column the third time (to disable sorting), the URL sent out towards the server is malformed : ...?%24format=json&%24inlinecount=allpages&%24top=5&%24orderby= which causes the server to fail.
This seems to be caused by the orderby= still being present, even though no sorting is applied. Is there any way of bypassing this without having to modify the sort function given in line 1542 of the unminified kendo.all.min.js not to assign the $orderby property when no actual data is present?
I have a sortable grid that's bound to a kendo dataSource with the following transport configuration:
transport: {
read: {
url:
"http://localhost/myJsonService"
,
dataType:
"json"
,
},
parameterMap: kendo.data.transports.odata.parameterMap
}
Everything works fine when I'm sorting a column in ascending/descending order, but when I click on the column the third time (to disable sorting), the URL sent out towards the server is malformed : ...?%24format=json&%24inlinecount=allpages&%24top=5&%24orderby= which causes the server to fail.
This seems to be caused by the orderby= still being present, even though no sorting is applied. Is there any way of bypassing this without having to modify the sort function given in line 1542 of the unminified kendo.all.min.js not to assign the $orderby property when no actual data is present?