Question

My baldness is growing more rapidly than it should be. I first posted this question a couple days ago. I now know the problem and have it working… sort of. Another problem surfaced in it’s place.

To solve the previous problem, I manually created the name to requestedDays[{0}].DateOfLeave where {0} was a Guid. This allowed my controller to properly receive the List<> of values.

Using this article’s method, the name generated is requestedDays[{0}].DayRequested.DateOfLeave which my controller doesn’t properly receive because the name has the class in it, DayRequested.DateOfLeave.

    [Authorize, HttpPost]
    public ActionResult Create(LeaveRequest leaveRequest, List<DayRequested> requestedDays)
    {
    }

I have tried to figure out work-arounds with the manual generation, but nothing I have tried works thus far. You can see my validation method here. I do know about the second part of Sanderson’s article on validation however, it is quite hard to validate something that isn’t being passed into the method.

This is my ViewModel I am using in my partial view.

public class LeaveRequestRow
{
    public LeaveRequestRow(DayRequested dayRequested, List<SelectListItem> leaveRequestType)
    {
        this.DayRequested = dayRequested;
        this.LeaveRequestType = leaveRequestType;
    }

    public List<SelectListItem> LeaveRequestType { set; get; }
    public DayRequested DayRequested { set; get; }
}

Does anyone have any ideas on how to proceed? Should I convert my dropdown to a jQuery build control and stop using the ViewModel?

Answer 1

I have solved this, though not as elegantly as I had hoped. All TextBoxFor had to be changed to TextBox along with the addtional changes needed with doing this. The names then were correctly generated and I could move on. This did break the ability for the validation message to appear next to the field, though ValidationSummary still does work. I will be working on fixing that later on and post code samples and a solution on my website.