在Entity Framework Core插入时如何合并同主键的重复Owner实体？

我正在开发一个从MS Graph获取带有所有者的Entra ID应用的程序，将每个Entra ID应用映射为Application实体，所有者映射为关联该应用的Owner实体。处理完所有Entra ID应用后，多个Application实体包含主键相同的Owner实体，导致SaveChangesAsync()报错。

现有处理代码 #

var applicationEntities = (await _assetOwnershipRepository.GetApplicationsAsync(includeOwners: true)).ToList();
var graphApplications = (await GetApplicationsAsync()).ToList();

graphApplications.ForEach(ua =>
{
    var applicationEntity = applicationEntities.FirstOrDefault(a => string.Equals(a.Id.ToString(), ua.Id, StringComparison.CurrentCultureIgnoreCase));

    if (applicationEntity is null)
    {
        var application = _mapper.Map<Application>(ua);
        _assetOwnershipRepository.AddApplicationsAsync(new[] {application});
        return;
    }
        
    _mapper.Map(ua, applicationEntity);
});

实体定义 #

Application实体 #

public class Application
{
    [Key] public Guid Id { get; set; }
    [Required] public Guid AppId { get; set; }
    [Required] [MaxLength(256)] public string DisplayName { get; set; } = default!;
    public ICollection<Owner> Owners { get; set; } = new List<Owner>();
}

Owner实体 #

public class Owner
{
    [Key] public Guid Id { get; set; }
    [Required] [MaxLength(256)] public string Name { get; set; } = default!;
    [Required] [MaxLength(256)] public string UserPrincipalName { get; set; } = default!;
    [Required] [MaxLength(256)] public string Email { get; set; } = default!;
}

解决方案 #

核心问题是EF Core上下文会跟踪实体实例，当多个主键相同但内存实例不同的Owner被添加时，上下文会判定为重复实体抛出异常。解决思路是确保每个主键的Owner在上下文中只有一个实例，具体实现如下：

方法一：先统一处理Owner，再关联到Application #

先提取所有Owner并去重，确保数据库/上下文里每个Id对应唯一实例，再将这些实例关联到Application：

var applicationEntities = (await _assetOwnershipRepository.GetApplicationsAsync(includeOwners: true)).ToList();
var graphApplications = (await GetApplicationsAsync()).ToList();

// 1. 提取所有Graph返回的Owner并按Id去重
var allGraphOwners = graphApplications
    .SelectMany(ua => ua.Owners)
    .DistinctBy(o => o.Id)
    .ToList();

// 2. 同步Owner：复用已有实例，新增不存在的Owner
var existingOwners = await _assetOwnershipRepository.GetOwnersAsync();
var ownerLookup = existingOwners.ToDictionary(o => o.Id);

foreach (var graphOwner in allGraphOwners)
{
    if (!ownerLookup.ContainsKey(graphOwner.Id))
    {
        var ownerEntity = _mapper.Map<Owner>(graphOwner);
        await _assetOwnershipRepository.AddOwnerAsync(ownerEntity);
        ownerLookup.Add(graphOwner.Id, ownerEntity);
    }
    else
    {
        // 可选：更新已有Owner的信息
        _mapper.Map(graphOwner, ownerLookup[graphOwner.Id]);
    }
}

// 3. 处理Application，关联上下文已跟踪的Owner实例
foreach (var ua in graphApplications)
{
    var applicationEntity = applicationEntities.FirstOrDefault(a => string.Equals(a.Id.ToString(), ua.Id, StringComparison.CurrentCultureIgnoreCase));

    if (applicationEntity is null)
    {
        var application = _mapper.Map<Application>(ua);
        // 替换为上下文已存在的Owner实例
        application.Owners = ua.Owners.Select(o => ownerLookup[o.Id]).ToList();
        await _assetOwnershipRepository.AddApplicationsAsync(new[] { application });
    }
    else
    {
        _mapper.Map(ua, applicationEntity);
        // 清空旧关联，重新绑定统一的Owner实例
        applicationEntity.Owners.Clear();
        foreach (var owner in ua.Owners)
        {
            applicationEntity.Owners.Add(ownerLookup[owner.Id]);
        }
    }
}

// 统一保存所有变更
await _assetOwnershipRepository.SaveChangesAsync();

方法二：通过AutoMapper自定义映射复用Owner实例 #

配置AutoMapper，在映射Owner时优先从上下文查找已存在的实例，不存在再创建：

// AutoMapper配置文件中添加
CreateMap<GraphOwner, Owner>() // 替换为MS Graph返回的Owner类型
    .ConstructUsing((source, context) =>
    {
        var dbContext = context.GetInstance<YourDbContext>(); // 获取你的EF上下文
        var existingOwner = dbContext.Owners.Find(source.Id);
        return existingOwner ?? new Owner();
    })
    .ForMember(dest => dest.Id, opt => opt.MapFrom(src => src.Id))
    .ForMember(dest => dest.Name, opt => opt.MapFrom(src => src.Name))
    .ForMember(dest => dest.UserPrincipalName, opt => opt.MapFrom(src => src.UserPrincipalName))
    .ForMember(dest => dest.Email, opt => opt.MapFrom(src => src.Email));

使用此配置后，映射Application时会自动复用上下文已有的Owner实例，避免重复。

注意事项 #

• 确保从MS Graph获取的Owner.Id是唯一且正确的，这是去重的核心依据
• 尽量在批量处理时先完成Owner的同步，再处理Application的关联，减少上下文跟踪冲突
• 如果使用仓储模式，确保仓储方法正确处理实体的跟踪状态

内容的提问来源于stack exchange，提问作者Shuzheng