Question 170706 in ASP.NET Question posted in
The official documentation can be found here.

Can Asp.net edit one-to-one parent & child together?

I have following parent and child models

    public class Director
    {
        public int ID { get; set; }
        public Home? Home { get; set; }
    }

    public class Home
    {
        public int ID { get; set; }
        public int DirectorID { get; set; }
        public Director Director { get; set; } = null!; 
        public string Location { get; set; } = string.Empty;
    }

Is there a good way to edit director and home together?
Currently, I always have the ModelState error that ErrorMessage [string]: "The Director field is required."

In the htmlcs, I use the following to update the home location inside director edit page.

            <div class="form-group">
                <label asp-for="Director.Home.Location" class="control-label"></label>
                <input asp-for="Director.Home.Location" class="form-control" />
                <span asp-validation-for="Director.Home.Location" class="text-danger"></span>
            </div>
Tags:

2

Answers


  1. 0

    The error message "The Director field is required" suggests that the framework is expecting a Director object in the Home model, but it’s not receiving one.

    Your models suggest a one-to-one relationship between Director and Home. In your Director model, Home is nullable, so it’s not required. But in your Home model, Director is not nullable and therefore required.

    In your view, you’re allowing the user to input the Home.Location, but not providing any mechanism to specify the Director associated with that Home.

    You have a few options to solve this:

    Modify your models to make Director nullable in your Home model.

    public class Home
{
    public int ID { get; set; }
    public int DirectorID { get; set; }
    public Director? Director { get; set; }
    public string Location { get; set; } = string.Empty;
}

    This way, the framework will not require a Director object when creating or modifying a Home. Note that this might not be the best approach, especially if every Home should logically be associated with a Director.

    Add a hidden input field for DirectorID in your view.

    <input type="hidden" asp-for="Director.Home.DirectorID" />

    This will allow you to associate the Home with a Director without having to modify your model, but it requires that you have the DirectorID available in your view model.

    If you are using Entity Framework, you can use the Include() method to load the Director object with the Home when you’re getting the data from your database.

    var director = _context.Directors
    .Include(d => d.Home)
    .FirstOrDefault(d => d.ID == id);

    This way, when you send the Director object to the view, it will already have a Home object associated with it, and the Director object within that Home will also be set.

    Remember to properly validate and handle all inputs and associations in your controller actions to ensure the integrity of your data. For example, when updating the Director and Home objects, you might need to check if the Home object already exists and then either create a new one or update the existing one.

    Login or Signup to reply.
  2. 0

    The simple answer is – do not use your entities as models (there are multiple reasons for this, including things like overposting attacks), create special classes for this goal. For example:

    public class DirectorUpdateModel
{
    public int ID { get; set; }
    public HomeUpdateModel Home { get; set; }
}

public class HomeUpdateModel
{
    public int ID { get; set; }
    public string Location { get; set; } = string.Empty;
}

    And entities to models for views and then map them back to corresponding entities.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search