Entity Framework model as Request Model

Question

I am trying to create Post API, which has following Model as request

public partial class Employee
    {
        public Employee()
        {
            EmployeeDetails = new HashSet<EmployeeDetail>();
        }

        public int Id { get; set; }
        public string? Name { get; set; }
        public string? Gender { get; set; }
        public int Age { get; set; }

        public virtual ICollection<EmployeeDetail> EmployeeDetails { get; set; }
    }

 public partial class EmployeeDetail
    {
        public int Id { get; set; }
        public int? EmployeeId { get; set; }
        public string? Details { get; set; }

        public virtual Employee Employee { get; set; }
    }

and I have and Post API which accept in parameter EmployeeDetail

public async Task<IActionResult> Post(EmployeeDetail empDetail){
      

}

so for this getting error : 
Bad Request 400.

Code to insert empDetail,(Let assume Employee already exist in database so not binding any value with Employee object., and based on EmployeeId, inserting Employee detail in employeeDetail table.)

This is what swagger suggesting for body request.
{
  "id": 0,
  "employeeId": 0,
  "details": "string",
  "employee": {
    "id": 0,
    "name": "string",
    "gender": "string",
    "age": 0,
    "employeeDetails": [
      "string"
    ]
  }
}

//But I only want to pass 
{ 
  "id": 0,
  "employeeId": 0,
  "details": "string"
}

Note : Requirement is to use only DbContext Model only. Any solution Thanks in Advance.

ShubhamWagh · Answer 1 · 2022-11-13T15:27:43.063

0

You can use a separate DTO for your request and then fill the model from that Or if you want to use the same model you can set the Employee property as internal or protected or private so the swagger can ignore it.

This is applicable to swashbuckle Swagger

Reference for DTO

How to configure Swashbuckle to ignore property on model

edited Nov 13 '22 at 15:27

answered Nov 13 '22 at 15:05

ShubhamWagh

565
2
9

Thanks for answer, but requirement is to use only DbContextModel. – MMJ89 Nov 13 '22 at 15:15
It is really requirement? Changing API or vice versa will force changing database model. Do you think this is ok? – Svyatoslav Danyliv Nov 13 '22 at 15:34
@SvyatoslavDanyliv you are correct, but I want to find any other solution. thanks for reply – MMJ89 Nov 13 '22 at 16:21

score 0 · Answer 2 · answered Nov 14 '22 at 02:06

There're two solutions may meet your requirement:

Solution1:

modify the property in your EmployeeDetails Model

public virtual Employee? Employee { get; set; }

Solution2:

disable the null validation in your csproj file as below:

<PropertyGroup>
    <TargetFramework>net6.0</TargetFramework>
    ......
    <Nullable>disable</Nullable>
    ......
  </PropertyGroup>

Entity Framework model as Request Model

2 Answers2