This walkthrough shows you how to use overrides to allow multiple tenants to share the same data connector, dashboards, etc., but have them display data from a different database for each tenant if they have the same structure. For example, each tenant might maintain their own database, or you may decide to use separate databases for security reasons.
2. Example setup
The following steps walk through setting up a simple example of a dashboard shared between tenants but displaying different data for each.
2.1. Set up tenant data sources
Create a database with a single table for the first tenant as follows:
- Database name: DatabaseA
- Table name: Products
- Column: ProductID, int
- Column: ProductName, nvarchar(50)
- Column: ListPrice, decimal(18,2)
Create a DatabaseB for the second tenant with the exact same schema (but different data) as above.
2.2. Create a new project and dashboard
Log on to Dundas BI as a System Administrator and create a new project. Do not select a specific tenant so that it will be accessible to all tenants, and make it the active project.
Create a new data connector for DatabaseA.
Then create a new dashboard by dragging the ListPrice and ProductName columns from your data connector to the dashboard canvas.
A table visualization is displayed, showing values from DatabaseA.
Check in your dashboard.
Go to the main menu and click Admin. Expand the SaaS / Multi-Tenancy section and click Tenants. (If you don't see this option, it means you aren't licensed for this feature.)
Click Add New in the toolbar.
In the Add Tenant dialog, enter the Name as TenantA.
Expand the Seat Allocation section and add 5 Standard User seats under Reserved.
Click the submit button at the bottom to add the tenant.
Repeat the above steps in order to add TenantB. The Tenants screen is updated with the list of tenants.
Next, go to the Admin screen, expand Account Service and click Accounts. Add a new account (UserA) and set its Tenant field to TenantA.
Similarly, add a new account (UserB) and set its Tenant field to TenantB. The list of accounts looks like this now:
3. Add data connector overrides
Under SaaS / Multi-Tenancy in the Admin section, go to Tenants, and click to edit TenantB (in our example).
Click Data connector overrides and then Add override.
In the Open dialog, choose the data connector to override for this tenant and click the submit button at the bottom.
In the data connector dialog, update the settings required to connect to the data source for this tenant (e.g., DatabaseB).
Submit the dialogs to add the override for the tenant.
4. View the dashboard as a tenant user
Log out of Dundas BI and log back on as UserA.
View the dashboard and observe that it displays the correct data from DatabaseA.
Log out again and log back on as UserB.
View the dashboard and observe that it displays the correct data from DatabaseB.
5. Using tenant time dimension overrides
Tenant time dimension overrides allow for a single time dimension's settings to be changed per-tenant. An example of this is if tenant A and tenant B use a different day as the start of the week. The following steps apply a time dimension override:
Edit a tenant from the Tenants page in Administration as shown above for data connector overrides. In the Tenant Details dialog, click Time dimension overrides.
Click Add override. In the Open dialog, select a time dimension to override.
In the Time Dimension dialog, change the options as required for this tenant, then submit the dialogs.