Audit EF is saving an Inserted action when no insert actually happened.

Full reproduction: https://github.com/VictorioBerra/Audit.NET_EF_Issue200_RelatedEntitys

There are a few important things to note. One, is the automapper profile:

cfg.CreateMap<CatUpdateViewModel, Cat>()
    .ForMember(dest => dest.CatBreedLine,
        opts => opts.MapFrom(src => src.CatBreedIds.Select(id => new CatBreedLine()
        {
            CatId = id,
            CatBreedId = src.Id
        })));

You can see, for every CatUpdateViewModel that I map to a Cat entity, it creates new instances of CatBreedLine.

Anyways, if you run the sample, look at the console output, notice no second insert for a CatBreedLine happened, yet Audit.EF saves an Insert audit record!!

Also, I would like EF to NOT bump the Created*/Updated* stuff for the CatBreedLine too since the record didnt technically ever change…

[thepirat000]

I’m closing this since it doesn’t seem to be considered as an issue for EF, it’s more a design decision and I don’t think this behavior is going to change.

So for your case, you should probably Include() the CatBreedLine on the Cat retrieval and have some logic instead of the VM->Cat mapping that overrides the lines.

[VictorioBerra]

Unfortunately, my Cat example was a huge simplification of a much bigger project with many relationships and entities and generic repos 😬 so it wont be that easy. But i appreciate the advice.