I currently have a kendo grid defined using Razor with read & update actions. It seems that, by default, the update action sends data as a url encoded string (application/x-www-form-urlencoded). Is there a way to set the datasource's update/create/delete actions to post json data instead. 

I ask because our grid rows contain nested objects used in business logic and we've found that the model binding process is really slow on a url encoded string, and very fast when we send the data as a json string (tested in a seperate ajax call).

Hello Matt,

You could configure the Grid for Ajax binding.  When configured for Ajax binding, the Grid for ASP.NET MVC makes Ajax requests when doing paging, sorting, filtering, grouping, or when saving data. A runnable example is available in the demo section for the Grid. You could also check the demo for Popup Editing.

Let me know if you have additional questions.

Regards,
Aleksandar
Progress Telerik

Hey Aleksandar, thanks for your reply! 

We do currently have the grid bound ajax. When we execute a read request the data is sent down from the server as json. However when the Update action is called the data is posted to the server as a form encoded url. We would like to have the data posted as a json encoded string, in a similar fashion as if the following javascript code had been called (but with only updated rows)

Thanks!

Hi Matt,

In this scenario, you would have to convert to Custom DataSource as shown in this demo and customize the parameterMap function. This function is used to convert the request parameters in a format that is suitable for the remote service. The Grid configuration would be similar to the below:

.Transport(t=> {
   ...
                    t.Update(u => u.Action("UpdateAction", "MyController").DataType("json").Type(HttpVerbs.Post));
                    t.ParameterMap("parameterMap");
   ...
                })

function parameterMap(data, operation) {
        if (operation === "update") {
            returnJSON.stringify(data);
            } 
   ...
}

I hope this helps.

Regards,
Aleksandar
Progress Telerik

Thanks for the reply, so I've implemented the change you mentioned, and now it seems that when my grid calls read I get back json data, but it doesn't bind correctly to the grid (I get one empty row).

Chrome debugger shows the data coming back, but when I call sender.dataSource.data() in the data bound event of the grid I get one object that has null values for all of my defined model fields, and the following Parameters. Data containing all of my rows, Total, an integer count of all of the rows, and then two null fields Aggregate Results and Errors. 

On the server in my controller I am calling .ToDataSourceResult. Is that not supported in a custom datasource? Or do I have to manually map back somehow?

I'm attatching my data source configuration below: 

DataSource:

Parameter Map Function: 

Hi Matt,

The ToDataSourceResult method used in the Controller action method wraps the data passed to the view in a Data object. In the scenario when CustomDataSource is used you would need to update the Schema to specify which part of the response contains the data:

.Schema(schema => {
    schema.Model(.....);
    schema.Data("Data");
    schema.Total("Total");
})

If you are passing back Aggregate results, Total and Errors you would need to configure those options in the Schema as well.

Regards,
Aleksandar
Progress Telerik

Ok, so I added those lines and now the grid is binding to data correctly. Now I'm running into the case where when I stringify the data in the parameterMap function the list of models allong with any additional data I pass doesn't bind on the server. 

Looking in chrome debugger it seems that my call to the update function is still sending "application/x-www-form-urlencoded" as the content type even though the DataType on the update function is set to "json" (see above). Is this incorrect? I tried setting the DataType to application/json but that also did not work.

Hi Matt,

With batch updates enabled you will need to add the Bind Attribute to specify the prefix that should be used to bind your complex object:

[AcceptVerbs(HttpVerbs.Post)]
public ActionResult Update([DataSourceRequest] DataSourceRequest request, [Bind(Prefix = "models")]IEnumerable<MyViewModel> updatedModels)
{
...
}

Check this demo for additional details on batch updating.

Let me know if this suggestion helps. If not please share the controller configuration of the update method?

Regards,
Aleksandar
Progress Telerik

Hey, sorry for the lack of clarity in my part. 

So this is what the update method signature looks like: 

and what's actually happening is that we're not binding any of the parameters, which results in an error because MVC can't find the configurationId parameter. 

If I make configurationId nullable then I get null values for both the models parameter and the configurationId parameter. 

I wanted to make sure that the data I was sending was correct, so I modified my parameter mapping function to store off its reults when I call the grid's normal SYNC method

After calling save and getting an error, I can then call the following code that sends the same set of mapped parameters but via explicit ajax. When I do this everything binds correctly.

What I've noticed, and I think this is the issue, is that the content type on the ajax call made via the grid sync method is still set to application/x-www-form-urlencoded (reported in the network tab of Chrome's dev), even though I have explicitly set the update method to send json (see my previously posted transport section). The actual json content does appear in the document body, because if I manually open up the input stream belonging to the .Net HttpRequest in my controller using something like the following, the data is all there.

I think that, because of how the content type is set, MVC's model binder looks for url encoded parameters in form data instead of in the posted body, so nothing binds.

Am I missing something in my transport definition? Or is there a bug in my version (Kendo UI v2018.3.1017)? 

Thanks!

Hello Matt,

Thank you for the additional details. I noticed I have misled you in one of my previous responses and I sincerely apologize for that. The DataType configuration specifies the result expected from the server, but not the type that would be sent. Thus your observation is indeed correct - by default the content type is set to "application/x-www-form-urlencoded". To configure the content-type HTTP header sent to the server use the .ContentType() configuration option:

transport.Update(update =>
            {
                update.Action("SaveProgress", "CustomPriceEntry")
                        .Data("priceEntryReadData")
                        .ContentType("application/json")
                        .DataType("json")
                        .Type(HttpVerbs.Post);
                 
            });

Setting the ContentType to "application/json" should resolve the issue.

Regards,
Aleksandar
Progress Telerik