AutoMapper - mapping nullable properties

While implementing AutoMapper in some existing code, I came across the need to map to a nullable property. Other business logic relied on this particular long being null instead of 0. The DTO has a property that contains a (long)Id, but the Entity contains the virtual property as well as a nullable long? of the Id. Anyway after fumbling through a few tries, I finally came upon the solution and wanted to share it here.

In the MapperProfile for the direction of DTO to Entity you have to do a null check, but the trick for me was having to explicitly cast to (long?)null.

CreateMap<ExampleDto, ExampleEntity>().ForMember(ee => ee.ExampleId, options => options.MapFrom(ed => ed.ExampleProperty != null ? ed.ExampleProperty.ExampleId : (long?)null)).NoVirtualMap();

Hope someone else finds this helpful, and finds it here.

14 points · 6 comments · view on lemmy.world

6 Comments

BeepStreet@lemmy.world · 2 pts · 3y (5 replies)

Wouldn't this work just as well? ed => ed.ExampleProperty?.ExampleId

zeroadam@programming.dev · 1 pts · 3y (4 replies)

I can certainly test this. My question would then be, will this result in actually mapping a null in the dto, or would the .ExampleProperty? just "be null" and cause the long property to instantiate to 0?

BeepStreet@lemmy.world · 1 pts · 3y

One way to find out ;) not sure...

dbilitated@aussie.zone · 1 pts · 3y (2 replies)

i'm pretty sure it'll be a long? - did you try it?

zeroadam@programming.dev · 1 pts · 3y (1 reply)

So.. When I change...

.ForMember(ee => ee.ExampleId, options => options.MapFrom(ed => ed.ExampleProperty != null ? ed.ExampleProperty.ExampleId : (long?)null))

TO:

.ForMember(ee => ee.ExampleId, options => options.MapFrom(ed => ed.ExampleProperty?.ExampleId))

I am presented with: CS8072 - An expression tree lambda may not contain a null propagating operator.

dbilitated@aussie.zone · 2 pts · 3y

there you go! thanks for updating, good to know