- Template: app
- Created ABP Studio Version: 2.1.2
- Current ABP Studio Version: 2.1.6
- Tiered: No
- Multi-Tenancy: Yes
- UI Framework: blazor-webapp
- Theme: leptonx
- Theme Style: system
- Theme Menu Placement: side
- Database Provider: ef
- Database Management System: postgresql
- Separate Tenant Schema: No
- Mobile Framework: maui
- Public Website: Yes
- Social Login: Yes
- Include Tests: Yes
- Kubernetes Configuration: Yes
- Distributed Event Bus: rabbitmq
- Use Local References: No
- Optional Modules:
- GDPR
- FileManagement
- TextTemplateManagement
- LanguageManagement
- AuditLogging
- Chat
- OpenIddictAdmin
- Selected Languages:
Arabic, Chinese (Simplified), Chinese (Traditional), English, English (United Kingdom), French, German (Germany), Hindi , Italian, Russian, Spanish
- Default Language: Arabic
- Create Command: abp new Jdoe.Pci -t app --ui-framework blazor-webapp --mobile maui --database-provider ef --database-management-system postgresql --theme leptonx --skip-migration --skip-migrator --public-website --without-cms-kit --sample-crud-page --dont-run-install-libs --dont-run-bundling -chat -file-management
I have a module and entities defines within that modules which some extend from IMultiTenant. I wonder what would be the best approach to load tenant details for a record when returning result to ui via Dto? I dont think it would be a good practice to add a navigation property on the the entity to the Tenant. I also dont have access to the ITenantRepository in the application in my module to query the tenant, which again I dont believe it would be a best approach when trying to follow the DDD.