sub objects cause not reaching the controller

[Robert]

Currently we have complicated model which has objects.

 

Model:

class Person {
string name{get; set;}
ContactInfo contactInfo{get; set;}
}

class ContactInfo  {
string phoneNumber {get; set;}
string address{get; set;}
}

 

View:

 @(Html.Kendo().Grid(Model.Person).Name("testGrid")
.Columns(columns =>
{
 columns.Bound(x => x.name);
columns.Bound(x => x.ContactInfo.phoneNumber);
....

 

 

in JS Console, with "$("#testGrid").data("kendoGrid").dataSource.data()" I see everything is good at the first load.

 

However, when I edit "phonenumber", the datasource looks like this:

o
-> Person 
     ->Name:"xxx"
     ->ContactInfo
            ->phoneNumber :"xxxx"
             ->address : "xxxxxx"
     ->ContactInfo.phoneNumber: ""

 

we used Jquery.ajax to send the data in js so it has duplicated "ContactInfo.phoneNumber" after stringify, then it never reaches the MVC controller.

 

Questions:
1. How to solve this issue?
2. How to avoid this additional "ContactInfo.phoneNumber" been created?

Thanks!

[Vasil]

Hi Robert,

The grid and its datasource are designed to bind to flat data only.

To make this work correctly you may want to add new model that combines all properties inside it. Something like:

class PersonCustomModel {
string name{get; set;}
string phoneNumber {get{return contactInfo.phoneNumber}; set{contactInfo.phoneNumber = value};}
string address{get{return contactInfo.address}; set{contactInfo.address = value};}

ContactInfo contactInfo{get; set;}
}

Then you can bind your columns directly to the "phoneNumber" same way as for the "name"

Regards,
Vasil
Telerik by Progress

[Robert]

Yes. that's the way we are doing by flatten out the objects. However, we have more than one layer and webapi. This way makes things complicated with a lot of the same mapping. In addition, we have way more fields than this samples which we try to avoid these kind of mapping manually. The client also requests the clean code without doing all those.

May I know if dot property is always empty? if so, we can write a JS method hack to delete all dot properties before sending.

thanks

 

 

[Vasil]

Hello Robert,

You could probably delete the excessive properties. But it is not guaranteed that it will work in wall cases, because it is not meant to be used that way.

Regards,
Vasil
Telerik by Progress