I have temporarily worked around this issue by flattening our data. Now I am trying to let users edit a single field, however Kendo seems to be acting a little funny.
First, the system submits ALL fields in the model, whether they have changed or not. This is bad on a number of accounts for us (auditing, repudiation, performance, etc.). How do I tell Kendo to only submit the deltas?
Second, the additional fields it is submitting are being submitted as null. Is this by design? On the server, here is what we get for two values. The first is a string I had provided as "null" and the other was just a NULL value that Kendo submitted.
Request.Form["String1"] == ""null"" (note the extra quotes, this is the string value of "null" quotes in included)
Request.Form["OtherValue"] == "null" (note only in one set of quotes, because this is the string "null", with no quotes)
What is the best practice for submitting NULL values in Kendo? Am I supposed to special case this on the server by pre-processing the Request.Form object?
Thanks!
First, the system submits ALL fields in the model, whether they have changed or not. This is bad on a number of accounts for us (auditing, repudiation, performance, etc.). How do I tell Kendo to only submit the deltas?
Second, the additional fields it is submitting are being submitted as null. Is this by design? On the server, here is what we get for two values. The first is a string I had provided as "null" and the other was just a NULL value that Kendo submitted.
Request.Form["String1"] == ""null"" (note the extra quotes, this is the string value of "null" quotes in included)
Request.Form["OtherValue"] == "null" (note only in one set of quotes, because this is the string "null", with no quotes)
What is the best practice for submitting NULL values in Kendo? Am I supposed to special case this on the server by pre-processing the Request.Form object?
Thanks!