auto-mapping | Auto mapping with AutoMapper and Reflection in ASP.NET Core | Reflection library

I'm trying to implement a very basic Spring Boot web application. In that I map a JSON object to an entity (says Customer Entity) with the help of @RequestBody.

In addCustomer method, I want to bind/map only the firstName & lastName fields and ignore Id field even if the client response JSON has that field.

And in updateCustomer method I need to map all the fields including Id because I need Id field to update the entity.

How can I ignore some or one field in auto-mapping process of the @RequestBody.

First, I adopted a project due to a developer jumping ship, so not only is this my first experience with .net core, but I'm having to digest a large code-base that I didn't write.

I need to know where to look to resolve an issue. I have a view that renders in a table a list of records.

Here are the relevant classes accessed:

I work with Dapper and I try to create auto-mapped method for inner join.
This is the example of the models:

I've been experiencing a lot of weird things with the Entity Framework designer in visual studio 2015 Professional. If I try to updated the model from the database it will delete all of the mappings of existing entities and replace the mappings with only the one I updated. If I add a relationship to existing entities it will delete all existing entity classes. The only way to update anything in the designer is to write it all out in XML.

Am I doing something wrong or is there something wrong with the file integrity maybe? I've found workarounds that say I have to completely delete the model and redo it from the database every time if I want to make a change. Updating the Model from the database. Even with this the auto-mapping isn't correct.

It shouldn't be this difficult, that's why I'm lead to believe that maybe something in the files that is making it lose it's integrity after copying it from the previous developer. Or is something else maybe the culprit?

Is it possible to leverage the NEST auto-mapping features to obtain Nest Property and Type objects without actually writing them into the elastic index via PUT Mapping and Create Index APIs?

For example, I'd like to auto-map this CLR class Company:

I have a POCO that has a coordinate field, and the mapping and geodistance search with NEST all works as expected. However, what I'm trying to do with NEST is to also return the distance from the point specified in the GeoDistance query as part of the search results. My research thus far indicates that there are two ways to do this:

• request a sort on the location
• create a script field as part of the query that runs the distance calculation inline

I decided to run with option 2, and here's what some of the code looks like:

I have seen similar answer here:

Spring MVC: Complex object as GET @RequestParam

Spring map GET request parameters to POJO automatically

I really can't find document of this because this auto mapping is not even done by any annotation. (it doesn't even need @RequestParam in fact)

1) so far I only see simple mapping, the object contain all primitive data, how about if my request is a complicated JSON object which contain several level of attributes (a object contain other objects)? Will the auto-mapping still work?

2) so far I only see Spring controller can take in one auto-map object, can I let it auto-map more than one object? For example: