Complex object and model binder ASP.NET MVC

Question

I have a model object structure with a Foo class that contains a Bar with a string value.

public class Foo
{
    public Bar Bar;
}

public class Bar
{
    public string Value { get; set; }
}

And a view model that uses that structure like this

public class HomeModel
{
    public Foo Foo;
}

I then have a form in view that in Razor looks something like this.

<body>
    <div>
        @using (Html.BeginForm("Save", "Home", FormMethod.Post))
        {
            <fieldset>
                @Html.TextBoxFor(m => m.Foo.Bar.Value)
                <input type="submit" value="Send"/>
            </fieldset>
        }

    </div>
</body>

In html that becomes.

<form action="/Home/Save" method="post">
    <fieldset>
        <input id="Foo_Bar_Value" name="Foo.Bar.Value" type="text" value="Test">
        <input type="submit" value="Send">
    </fieldset>
</form>

Finally the controller to handle the post loos like this

[HttpPost]
public ActionResult Save(Foo foo)
{
    // Magic happends here
    return RedirectToAction("Index");
}

My problem is that Bar in Foo is null once it hits the Save controller action (Foo is created but with an null Bar field).

I thought the model binder in MVC would be able to create the Foo and the Bar object and set the Value property as long as it looks like the above. What am I missing?

I also know my view model is a bit over complicated and could be simpler but I for what I'm trying to do I'd really help me if I could use the deeper object structure. The examples above uses ASP.NET 5.

Your post method parameter needs to be HomeModel or you need to use the [Bind(Prefix="foo")] attribute. But you should never name a parameter in an ActionResult method with the same name as a model property (binding will fail) — user3559349
– user3559349, Commented Jan 29, 2015 at 10:16
@StephenMuecke thanks for the response. I did however change to receive HomeModel in the Save action and changed the parameter name - but still an empty object in Foo ... — Riri
– Riri, Commented Jan 29, 2015 at 10:26
That's because its a field, not a property. Add the getter and setter :) — user3559349
– user3559349, Commented Jan 29, 2015 at 10:28
@StephenMuecke dammit ... I thought I could use fields ... Didn't event think of changing that ... Thanks! Just change your comment to a post if you want the points. — Riri
– Riri, Commented Jan 29, 2015 at 10:32
@Riri, thanks for giving a simple example. I have to confess I'm getting upset about how often the reverse happens (which is purely the questioner's fault of course). I'm sorry if this is a meta note, but after wading through so many contrary bloated examples on this related question, it was refreshing. — Nicholas Petersen
– Nicholas Petersen, Commented Feb 16, 2016 at 22:59

user3559349 · Accepted Answer · 2015-01-30 02:17:33Z

44

Firstly, the DefaultModelBinder will not bind to fields so you need to use properties

public class HomeModel
{
  public Foo Foo { get; set; }
}

Secondly, the helpers are generating controls based on HomeModel but you posting back to Foo. Either change the POST method to

[HttpPost]
public ActionResult Save(HomeModel model)

or use the BindAttribute to specify the Prefix (which essentially strips the value of prefix from the posted values - so Foo.Bar.Value becomes Bar.Value for the purposes of binding)

[HttpPost]
public ActionResult Save([Bind(Prefix="Foo")]Foo model)

Note also that you should not name the method parameter with the same name as one of your properties otherwise binding will fail and your model will be null.

answered Jan 30, 2015 at 2:17

user3559349

Sign up to request clarification or add additional context in comments.

3 Comments

Nicholas Petersen Over a year ago

"should not name the method parameter with the same name as one of your properties otherwise binding will fail and your model will be null." -- Thanks a million for this note! But OH my goodness, what a frustrating gotcha. I'm sure there was some technical difficulty, but surely they could have overcome this unexpected and hard to ever discover limitation. Even with SO, I've read many articles before finding this one, and you could easily not have put this. It seems to me it would have been worth overcoming this limitation. Anyways, thanks a million.

user3559349 Over a year ago

@NicholasPetersen, You right that its frustrating and not obvious, but there is really no way to overcome this because of the way model binding works. The actual behavior is explained in a bit more detail in this answer. Its a pity that its not better documented.

ferr Over a year ago

Pulled my hair out for the past few hours over the properties vs fields gotcha. I can't believe it was something so simple as that. uggggggh

Nicholas Petersen · Accepted Answer · 2016-02-16 23:04:32Z

2

I just discovered another reason this can happen, which is if your property is named Settings! Consider the following View model:

public class SomeVM
{
    public SomeSettings DSettings { get; set; } // named this way it will work

    public SomeSettings Settings { get; set; } // property named 'Settings' won't bind!

    public bool ResetToDefault { get; set; }
}

In code, if you bind to the Settings property, it fails to bind (not just on post but even on generating the form). If you rename Settings to DSettings (etc) it suddenly works again.

answered Feb 16, 2016 at 23:04

Nicholas Petersen

9,6087 gold badges62 silver badges74 bronze badges

Comments

Community · Accepted Answer · 2017-05-23 12:34:41Z

0

I had the same problem and after I followed @Stephen Muecke steps I realized that the problem was caused because my inputs were disabled (I was disabling them with JQuery on document ready) as you can see it here: How do I submit disabled input in ASP.NET MVC?. At the end I used read-only instead of disabled attribute and all the values were sent successfully to the controller.

edited May 23, 2017 at 12:34

CommunityBot

11 silver badge

answered Dec 6, 2016 at 16:06

joalcego

1,15412 silver badges17 bronze badges

Comments

Prisoner ZERO · Accepted Answer · 2017-09-26 14:24:30Z

0

I had the same problem, but once I created a HIDDEN FIELD for the foreign-key...it all worked just fine...

FORM EXAMPLE:

@using (Html.BeginForm("save", "meter", FormMethod.Post))
{
    @Html.AntiForgeryToken()
    @Html.ValidationSummary(true)

    @Html.HiddenFor(model => Model.Entity.Id)
    @Html.HiddenFor(model => Model.Entity.DifferentialMeter.MeterId)
    @Html.HiddenFor(model => Model.Entity.LinearMeter.MeterId)
    @Html.HiddenFor(model => Model.Entity.GatheringMeter.MeterId)

    ... all your awesome controls go here ...
}

ACTION EXAMPLE:

// POST: /Meter/Save
[HttpPost]
public ActionResult Save(Meter entity)
{
    ... world-saving & amazing logic goes here ...
}

PRETTY PICTURES:

answered Sep 26, 2017 at 14:24

Prisoner ZERO

14.2k21 gold badges103 silver badges150 bronze badges

Collectives™ on Stack Overflow

Complex object and model binder ASP.NET MVC

4 Answers 4

3 Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

3 Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related