I have been trying, for several days, to write HTML/JQuery that calls my ASP.Net MVC Controller and populates the DataSourceRequest structure properly. No matter what I tried, the values in the request for Filters and Sorts were null even though the paging information was present. I consulted the documentation and I found this unhelpful information in the DataSource documentation.
Loads transport with preconfigured settings. Currently supports only "odata" (Requires kendo.data.odata.js to be included).
Eventually I gave up and did, with hindsight what I should have done first, and that was to write a small test case using the helpers to see what it generated. And lo and behold MAGIC. If the type: attribute of the dataSource is set to aspnetmvc-ajax the DataSourceRequest fields are magically populated. So a code snippet is:
Now I am going to have a little gripe. A year ago i started using the Telerik Controls for ASP.Net and I was blown away by them - they were awesome and, for the most part I found the support pretty good. Because I was so impressed as I migrated to MVC I decided to move to Kendo UI because it seemed to be a very clean interface and I had been impressed by the earlier controls.
But it has proven to be a disaster. The product is inherently brilliant. But it's clearly not finished and, if you are like me, and work alone, it can be a nightmare solving each problem as it occurs one at a time. I'd like to say the forums help, and sometimes they do, but there are a depressing number of posts that have one of the following characteristics.
- They go unanswered for weeks, if not months - in fact it is not uncommon to see a follow up a week or so later by the original poster about how they eventually circumvented the problem.
- A Telerik employee posts nothing but a link to the documentation. The documentation is dreadful. It follows in the path of Microsoft documentation by which I mean if you already know the answer, or at least where to find the answer, it often answers your question. But if you have a "Where do I start with this?" type of question it is generally hopeless.The examples are like most examples in most books,- that is they are fairly simple and most of what developers do isn't simple. And the tricky parts are never answered.
As I suggested in a post several weeks ago, Telerik needs to commission someone like APress to write a book about Kendo UI so that someone who enjoys writing and explaining things can write some good documentation. I'd buy that book, or even better, I'd subscribe to an online version of it that was kept up to date as bugs were fixed and features added. Most developers, myself included, hate writing documentation and, in general, we are not good at it.
Anyway, there are my two roubles worth - overall, I love the product, but it has made this project I am working on very late. I wish I had stuck to regular ASP.Net with Telerik. But in the end I hope the pain will have been worth it.