Hello team,
I’m working with a modular solution in ABP Studio (latest version), and I've encountered an issue where I can't create navigation properties between entities from different modules.
Specifically:
I’m editing the Deal entity in the Esone.AdvertisingService module.
I need to create a navigation to the Brand and Branch entities, which are defined in the Esone.BrandingService module.
I have already added proper project references between the modules in the .csproj files, and the solution builds successfully.
However, when I open the "Navigations" tab in ABP Studio, entities from the BrandingService module do not appear in the entity selector, making it impossible to define the relationship through the UI.
I've also ensured that the namespaces and domain folders are properly structured, and that the entities are public and located in their respective Domain layers.
As a result, I have to define these relationships manually in the code (DbContext, entity properties, and EF mappings).
Is there any additional configuration required to enable cross-module entity navigation in ABP Studio?
2 Answer(s)
-
0
Hi,
We're investigating the case right now, Our ABP Suite team will respond as soon as possible to this issue
-
0
Hi,
Is there any additional configuration required to enable cross-module entity navigation in ABP Studio?
Unfortunately, currently, there is no out-of-the-box support for cross-module entity navigation. I'll create an issue for that. But in the meantime, if you look for a workaround, you can copy the related entity metadata from your module
Esone.BrandingService
(under the .suite/entities folder) and paste the related entity file (EntityName.json
) to the moduleEsone.AdvertisingService
and then establish 1-n relationship. But, please note that, while applying this approach, they can be missing namespaces and you may need to make some modifications.Regards.