9

I'm probably missing something very obvious, but all I'm trying to do is have a simple form, allow it to POST, change one of the fields, and when it returns it should show me the changed value. Simple, right?

The model looks like this:

public class TestModel
{
    public string Field1 { get; set; }
    public string Field2 { get; set; }
}

The controller actions:

public IActionResult Test()
{
    return View(new TestModel());
}

[HttpPost]
public IActionResult Test(TestModel model)
{
    model.Field1 = "changed"; // this seems to be ignored
    return View(model);
}

The view:

@model AspNetCoreTest1.Models.TestModel
<form method="post" asp-controller="Home" asp-action="Test">
    <input asp-for="Field1" />
    <br />
    <input asp-for="Field2" />
    <br />
    <button type="submit">Send</button>
</form>

I can see the form and it POSTs back (I can see the values I typed in the model), but after the POST the form still shows the values I typed. It does NOT show changed for the first field.

(I'm using ASP.NET Core 1.1)

Thoughts?

pbz
  • 8,865
  • 14
  • 56
  • 70

3 Answers3

7

We can't directly make changes to the model which is passed and hope for that it will reflect in UI. The solution for your problem is as follows.

Replace this line of code model.Field1 = "changed"; with following if you are using C# 6.0:

ModelState.FirstOrDefault(x => x.Key == nameof(model.Field1)).Value.RawValue = "changed";

For earlier C# versions:

ModelState.FirstOrDefault(x => x.Key == "Field1")).Value.RawValue = "changed";
Vedant
  • 203
  • 1
  • 6
  • OK... your code works, but, not intuitive to say the least (comment on the framework, not your answer). The official documentation passes the model back to the View (https://learn.microsoft.com/en-us/aspnet/core/tutorials/first-mvc-app/controller-methods-views) on POST. I just tried simply passing View() without the model and that also works; which makes sense given what you're saying. What's the benefit of it working this way? – pbz Jan 21 '17 at 17:46
  • After reading @CodeCaster 's link it now makes sense what it's going on behind the scenes. I still think it's a poor design decision. Thanks to both of you for your help – pbz Jan 21 '17 at 17:52
6

you can just call :

ModelState.Clear();
return View(YourModel);

this will clear all ModelState values

Ahmed Fouad
  • 61
  • 1
  • 2
1

Note: This is only a problem if you are using ASP.NET input controls. For example, if your HTML contains

<p>@model.Field1</p>

Then you can update Field1 in the controller

[HttpPost]
public IActionResult Test(TestModel model)
{
   model.Field1 = "changed"; // this will update as expected
   return View(model);
}

You only need to use the solution given by Vadent when your HTML contains

<input asp-for="Field1" class="form-control" />
wpqs
  • 657
  • 1
  • 7
  • 18