Open Closed

ABP Suite Internal Error When Creating Master Entity With Navigation Property to Child Entity #10793


User avatar
0
zhongquan.ooi created

Hi, I am facing the issue where I can generate the master entity with lets say BusinessUnitId (from BusinessUnit master entity). But it says internal error when i add LocationId (from Location child entity of BusinessUnit master entity). The logs say:

Could not find a part of the path C:\SourceCode\XX\test\XX.Domain.Tests\Locations\LocationsDataSeedContributor.cs

Markdown supported.
Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

8 Answer(s)
  • User Avatar
    0
    AI-Bot created
    Support Team ABP Agent
    • This error is not caused by the navigation property itself. ABP Suite is failing while trying to create/update the test data seeder file for the entity (because you enabled Create Tests during CRUD generation).
    • The log tells the exact failing file path Suite is trying to touch, but it doesn’t exist on disk:
    Could not find a part of the path
      C:\SourceCode\XX\test\XX.Domain.Tests\Locations\LocationsDataSeedContributor.cs
    

    Fix (fastest)

    1. Re-generate the entity with “Create Tests” unchecked in ABP Suite.
      • Suite will skip generating/updating *.Domain.Tests data seed contributors, so it won’t try to access that missing folder/file.

    Fix (keep tests enabled)

    1. Ensure your solution really has the expected test project/folder structure:
      • test\XX.Domain.Tests\
    2. Under that project, create the missing folder:
      • Locations\
    3. Then run generation again.

    Why it happens “only when adding LocationId”

    • When you add a navigation connection (especially master-detail / child references), Suite may additionally generate or update test seed contributors for the related entity (here: LocationsDataSeedContributor.cs). If the test\...Domain.Tests\Locations\ folder (or the XX.Domain.Tests project) isn’t present, you get this “Could not find a part of the path” internal error.

    Links (verified):

    • https://abp.io/docs/latest/suite/generating-crud-page
    • https://abp.io/community/articles/furp75ex

    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.

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    zhongquan.ooi created

    Hi, need support team assistance.

    Context: 1. Create Master entity called ProcessAprroval 2. Inside ProcessApproval entity, reference two entities as FK (BusinessUnitId and LocationId) 3. Getting internal error message if create by: adding both FK in the basics section of the navigation properties page in ABP Suite. 4. Able to save and generate the ProcessApproval entity if remove the LocationId FK in Navigation Properties page. 5. BusinessUnitId is the primary key of Business Unit master entity, then LocationId is sitting in the Location child entity of Business Unit master entity.

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    Hi,

    This is a Suite bug, not something wrong on your side. It shows up because Location is a child entity in a master-detail relationship. Child entities don't get their own data seed contributor generated under *.Domain.Tests, but when you add a required navigation property that points to one, Suite still tries to read that missing LocationsDataSeedContributor.cs while generating the test seeder for ProcessApproval — so it fails with the "Could not find a part of the path" error. That's also why removing LocationId lets it generate: BusinessUnit is a master entity and does have that file.

    As a temporary fix, uncheck Create unit & integration tests on the ProcessApproval entity and generate again:

    • Open ProcessApproval in Suite
    • On the Entity info tab, untick Create unit & integration tests
    • Save and generate

    Suite then skips the test seeders entirely, so it generates fine and your required BusinessUnitId / LocationId FKs stay as they are. You can turn tests back on and regenerate once it's fixed.

    We'll get this fixed on the Suite side.

    Thanks

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    Since this turned out to be a Suite bug, we've refunded your ticket.

    Thanks

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    zhongquan.ooi created

    Hi, do we have any info on when will this be fixed?

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    Hi,

    We've fixed it on our side, and it will ship in the next 10.5.x patch. Until then the workaround above (uncheck Create unit & integration tests for that entity) keeps you unblocked.

    Thanks

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    zhongquan.ooi created

    thanks.

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    : )

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
Boost Your Development
ABP Live Training
Packages
See Trainings
Mastering ABP Framework Book
The Official Guide
Mastering
ABP Framework
Learn More
Mastering ABP Framework Book
Made with ❤️ on ABP v10.8.0-preview. Updated on September 28, 2026, 11:44
1
ABP Assistant
🔐 You need to be logged in to use the chatbot. Please log in first.