Child Collections Not Returned in GET Endpoints Generated by ABP Suite #10242

2 Answer(s)

• 

  0

  AI-Bot created 8 hours ago

  Support Team ABP Agent

  1. Solution

  • Why it happens

    • EF Core does not enable lazy loading by default in ABP. The default repository GetAsync(id) loads only the aggregate root and not its navigation collections. Therefore, when the ObjectMapper maps ProductItem to ProductItemDto, the collections are not loaded and end up empty.

  • What to change

    • Load related collections explicitly, then map. Use ABP’s repository WithDetails/WithDetailsAsync (or GetAsync(id, includeDetails: true) if your repository exposes it) to eagerly include navigation properties.

  • Option A: Use WithDetailsAsync in your AppService

  public virtual async Task<ProductItemDto> GetAsync(Guid id)
    {
        var queryable = await _productItemRepository.WithDetailsAsync(
            x => x.ProductItemCultures,
            x => x.ProductItemAttributeListValues
        );
  
        var entity = await AsyncExecuter.FirstOrDefaultAsync(queryable.Where(x => x.Id == id));
        if (entity == null)
        {
            throw new EntityNotFoundException(typeof(ProductItem), id);
        }
  
        return ObjectMapper.Map<ProductItem, ProductItemDto>(entity);
    }
  

  • Option B: Expose includeDetails on repository Get/Find
    • If your repository inherits from EfCoreRepository, you can call:

  public virtual async Task<ProductItemDto> GetAsync(Guid id)
    {
        var entity = await _productItemRepository.GetAsync(id, includeDetails: true);
        return ObjectMapper.Map<ProductItem, ProductItemDto>(entity);
    }
  

  • Then configure default details in a custom repository if needed:

  public class ProductItemRepository 
        : EfCoreRepository<MyDbContext, ProductItem, Guid>, IProductItemRepository
    {
        public ProductItemRepository(IDbContextProvider<MyDbContext> dbContextProvider)
            : base(dbContextProvider)
        {
        }
  
        public override async Task<IQueryable<ProductItem>> WithDetailsAsync()
        {
            return (await GetQueryableAsync())
                .Include(x => x.ProductItemCultures)
                .Include(x => x.ProductItemAttributeListValues);
        }
    }
  

  • With this, any GetAsync(id, includeDetails: true) will include those navigations by default.

  • Notes for multi-tenancy and filters

    • Ensure the requested ProductItem and its children belong to the same Tenant (entities implement IMultiTenant). ABP’s data filters automatically apply tenant filtering; mismatched TenantId will result in not-found or empty collections.
    • If any child entities are soft-deleted (ISoftDelete), ABP filters them out. Disable filters only if you need to see deleted children:

  using (DataFilter.Disable<ISoftDelete>())
      {
          // load with details here
      }
  

  • Summary
    • Replace the generated GetAsync(id) call with an eager-loading variant (WithDetails/Include) so EF Core actually retrieves ProductItemCultures and ProductItemAttributeListValues before mapping. Swagger shows the DTO shape, not the loading behavior; you must include related data explicitly.

  2. Sources

  • Validated reference (ABP EF Core, Loading Related Entities – WithDetails/WithDetailsAsync):
    • https://abp.io/docs/latest/framework/data/entity-framework-core/

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Save Cancel
• 

  0

  chrisalves created 7 hours ago

  After trying to debug the issue, I found some possible cause:

  a) The mapper created by ABP Suite is ignoring the child entities that I need to be returned. See the picture below:

  b) Something is missing at the Repository created by default using ABP Suite.

  Save Cancel