Skip to main content
BuyLog In
XAF: Cross-Platform .NET App UI & Web API
Search in…
Docs > Multi-Tenancy (Data per Tenant) > Modules in a Multi-Tenant Application
All docs
V24.1
.NET 6.0+
XAF: Cross-Platform .NET App UI & Web API
Getting Started
Installation, Upgrade, Version History
Backend Web API Service
UI Shell and Base Infrastructure
Storage, ORM, and Business Model Design
Data Manipulation and Business Logic
User Interface and Behavior Customization
Data Filtering
Application Security and Data Safety
Multi-Tenancy (Data per Tenant)
Multi-Tenant Application Architecture
Create a new Multi-Tenant Application
Convert an Existing Application into a Multi-Tenant Application
Get the Current Tenant in Code
Modules in a Multi-Tenant Application
Validation (Prevent Data Errors)
Conditional Appearance (Manage State of UI Elements)
Reporting (Shape, Export & Print Data)
Analytics (Extract Data Insights)
Document Management
Business Process Management
Event Planning
Localization
Accessibility Support
Debugging, Testing and Error Handling
Deployment
Support, QA & Troubleshooting
API Reference
Download CHM

Modules in a Multi-Tenant Application

  • 2 minutes to read

Standard Module Support

In Tenant User interface mode, a multi-tenant application supports all standard modules in the same way as a single-tenant XAF application.

Host User Interface mode does not support some of the standard modules. The list of unsupported modules includes all modules that need to store their own persistent types in the database. This is because the Host User Interface restricts the types that are allowed to be stored to only the types required to manage users and tenants. Below is the list of standard XAF modules that cannot be used in a multi-tenant application when it runs in Host User Interface mode:

Custom Module Support

Keep the following specifics in mind when you develop a custom module in a multi-tenant application:

  • If a module registers its own persistent types to store in a database, this module cannot be used in Host User Interface mode.

  • Assume that you have a module that registers its own persistent types and includes controllers that operate on these types. In such case, when you query an ObjectSpace, always ensure that the required type is supported by this ObjectSpace instance. To do this, use the IObjectSpace.CanInstantiate method: objectSpace.CanInstantiate(typeof(YourPersistentType)).

  • When you implement logic used to update a database in Module Updater, both the Host Database and all Tenant Databases will be updated. Keep in mind that modules cannot store their persistent types in the Host Database.

  • Custom modules/business classes/custom fields per user/tenant are unsupported in the current version. At present, we recommend that you load all modules and business classes, and use a Controller to disable features per user/tenant instead. See the following topic for more information: Get the Current Tenant in Code. All tenants will have the same set of business classes and database tables in their own databases.

  • The Host User Interface does not allow users to manage available modules/features or licensing packages/editions for associated tenants and their users at application runtime. For future development, please also take a moment to complete a short survey on your multi-tenancy requirements: XAF UI & Web API Service: Your Vote Matters | DevExpress.