Search results

How to publish modified data sources from one tenant to another

To modify the connection string of the corresponding data source of a dashboard dynamically in the destination tenant using Custom Attribute support, create and save the required data source connection string details as custom attribute in both source and destination tenants with the same attribute key and use it in the dynamic connection string value of a corresponding data source in a dashboard of a source tenant.

Find the list of connections with the connection string details as follows,

  • Amazon Aurora MySQL

    { "Server": "", "Port": "", "Username": "", "Password": "", "Database": "", "AdvancedSettings": "", "Command Timeout": "300" }
  • Amazon Aurora PostgreSQL

    { "Server": "", "Port": "", "Username": "", "Password": "", "Database": "", "SslMode": "false", "TrustServerCertificateKey": "false", "AdvancedSettings": "", "CommandTimeout": "300" }
  • Amazon Redshift

    { "Server": "", "Port": "", "UID": "", "PWD": "", "Database": "", "Sslmode": "false", "Trust Server Certificate ": "false", "AdvancedSettings": "", "Command Timeout": "300" }
  • Azure SQL Data Warehouse

    { "Azure SQL Data Warehouse server name": "", "Username ": "", "Password": "", "Azure SQL Data Warehouse database name": "" }
  • Google Cloud SQL

    { "Database Engine": "", "Server": "", "Port": "", "User Id": "", "Password": "", "Database": "", "AdvancedSettings": "", "CommandTimeout": "300" }
  • MariaDB

    { "host": "", "port": "", "user": "", "password": "", "database_name": "", "AdvancedSettings": "", "CommandTimeout": "300" }
  • MemSQL

    { "host": "", "port": "", "user": "", "password": "", "database": "", "AdvancedSettings": "", "connectTimeout": "300" }
  • Microsoft SQL Server

    { "Data Source": "", "Initial Catalog": "", "User ID": "", "Password": "", "Integrated Security": "false", "AdvancedSettings": "" }
  • MySQL

    { "Server": "", "Port": "", "Username": "", "Password": "", "Database": "", "AdvancedSettings": "", "Command Timeout": "300" }
  • Oracle

    { "Server": "", "Port": "", "INSTANCE_NAME": "", "UserID": "", "Password": "", "AdvancedSettings": "", "CommandTimeout": "" }
  • PostgreSQL

    { "Server": "", "Port": "", "Username": "", "Password": "", "Database": "", "SslMode": "false", "TrustServerCertificateKey ": "false", "AdvancedSettings": "", "CommandTimeout": "300" }
  • Amazon RDS

    { "Data Source": "", "PortNumber": "", "User ID": "", "Password": "", "Initial Catalog": "", "Integrated Security": "false", "AdvancedSettings": "" }
  • CData with MySQL endpoints

    { "Server": "", "Port": "", "User": "", "Password": "", "Database": "", "AdvancedSettings": "", "Timeout": "300" }
  • InfluxDB

    { "bind-address": "", "username": "", "password": "", "auth-enabled": "true" }

Follow these steps to publish the modified data sources from one tenant to another

  1. First,you need to create a custom attribute with the required connection string in the source tenant.

    Custom Attribute of Source Tenant

  2. Edit the dashboard’s corresponding data source, enable the Dynamic Connection String option, and click on the Configure button.

    Enable Dynamic Connection String

  3. In that pop-up window, choose the Custom Attribute option, enter the created custom attribute key (Name) in the text box, select the Configuration Mode as Both if needed, and save the configuration. Finally, save that data source.

    Note: Refer to this section to learn more details about the Configuration Mode of Dynamic Connection String.

    Configure Dynamic Connection String

    Now, the dashboard will be rendered in the source tenant as shown in the following image.

    Dashboard in Source Tenant

  4. Then create the Custom Attribute with the required connection string details in the destination tenant with the same attribute key (Name) used on the source tenant as shown in the following image.

    Custom Attribute of Target Tenant

  5. Now, publish the dashboard in the source tenant configured with the modified data source to the destination tenant using the Publish dashboard in the internal site support. And we can ensure it by checking the status of the published dashboard by clicking on the Publish icon in left sidebar.

    How to publish dashboard in Target Tenant

    To Synchronize published dashboard to reflect dashboard changes in other sites, click Synchronize option then select Yes on the pop-window.

    Synchronize Option

    Synchronize Pop-up Window

    You will receive the following highlighted notification

    Synchronization Notification

  6. Refresh the destination tenant and open the dashboard. Now, the dashboard will be rendered with the data of the connection string, which is added to the custom attribute of the tenant.

    Dashboard in Target Tenant

NOTE: The published dashboard will work properly only if the source site’s data source schema matches the target site’s schema.