Loading navigation properties using LoadOptions.ForceIdentityResolution #9062

geoff.hardy created 3 days ago

We are instantiating multiple AssetForm entities and then call RepositoryExtensions.EnsurePropertyLoadedAsync method to load a navigation property.

await assetFormRepository.EnsurePropertyLoadedAsync(assetForm, o => o.ConservatorField);

When we save the entities to the database, an exception is thrown:

System.InvalidOperationException: The instance of entity type 'ConservatorField' cannot be tracked because another instance with the key value '{Id: 11}' is already being tracked. When attaching existing entities, ensure that only one entity instance with a given key value is attached

The underlying problem appears to be that the underlying EFCoreRepositoruy.EnsurePropertyLoadedAsync calls ReferenceEnty.LoadAsync with LoadOptions.None.

Ideally we would like to load these navigation properties using the LoadOptions.ForceIdentityResolution, so that we do not get this problem with multiple entities being tracked.

One option would be to subclass EFCoreRepository and override the EnsurePropertyLoadedAsync method to alter the behaviour.

Is there a better option to accomplish this?

ABP:9.0.2
UI: Angular
Database: EF Core
Tiered: yes

maliming created 2 days ago

Support Team Fullstack Developer

Can you share the code to reproduce?

If you can share a template project, that would be best.

Thanks.

liming.ma@volosoft.com

geoff.hardy created 2 days ago

I have emailed you a sample project, let me know if you have any questions.

Thanks!

maliming created a day ago

Support Team Fullstack Developer

maliming created a day ago

Support Team Fullstack Developer

Try this

book1.Author = await _personRepository.GetAsync(book1.AuthorId);
book2.Author = await _personRepository.GetAsync(book2.AuthorId);

public class BookAppService : ApplicationService, IBookAppService
{
    private readonly IRepository<Book, Guid> _repository;
    private readonly IRepository<Person, Guid> _personRepository;

    public BookAppService(IRepository<Book, Guid> repository, IRepository<Person, Guid> personRepository)
    {
        _repository = repository;
        _personRepository = personRepository;
    }

    public async Task<string> DoStuffAsync()
    {
        // Create two books
        var book1 = new Book { Name = "Book 1", AuthorId = AbpAngularSandboxConsts.Person1Id };
        var book2 = new Book { Name = "Book 1", AuthorId = AbpAngularSandboxConsts.Person1Id };

        // Populate the navigation properties, which would would be used by subsequent domain logic  prior to saving
        book1.Author = await _personRepository.GetAsync(book1.AuthorId);
        book2.Author = await _personRepository.GetAsync(book2.AuthorId);

        // At this point, both books have their Author referencing different objects, although they are the same entity in the database

        // Save the books.
        // This will fail with the following exception:
        // System.InvalidOperationException: The instance of entity type 'Person' cannot be tracked because another
        // instance with the same key value for {'Id'} is already being tracked. When attaching existing entities,
        // ensure that only one entity instance with a given key value is attached.
        // Consider using 'DbContextOptionsBuilder.EnableSensitiveDataLogging' to see the conflicting key values.
        await _repository.InsertManyAsync([book1, book2], true);

        return "Success";
    }
}