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,

• SQL

• Azure Synapse Analytics

• Amazon RDS SQL

  { "DataSource": "", "InitialCatalog": "", "UserName": "", "Password": "", "IntegratedSecurity": "", "AdvancedSettings": "", "CommandTimeout": "" }

• Amazon Athena

  { "Database": "", "RegionEndpoint": "", "OutputLocation": "", "AwsAccessKeyId": "", "AwsSecretAccessKey": "" }

• Amazon Aurora PostgreSQL

• Amazon Redshift

• Google Cloud PostgreSQL

• Amazon RDS PostgreSQL

  { "ServerName": "", "Database": "", "UserName": "", "Password": "", "Port": "", "SslMode": "", "TrustServerCertificate": "", "AdvancedSettings": "", "CommandTimeout": "" }

• ClickHouse

  { "ServerName": "", "Database": "", "Port": "", "UserName": "", "Password": "", "AdvancedSettings": "", "CommandTimeout": "" }

• Elasticsearch

  { "ServerName": "", "Database": "", "Port": "", "UserName": "", "Password": "", "AuthenticationType": "", "AdvancedSettings": "", "ConnectionType": "" }

• MySQL

• Amazon Aurora MySQL

• MariaDB

• Google Cloud MySQL

• Amazon RDS MySQL

• Amazon RDS MariaDB

• CDATA with MySQL endpoints

• SingleStore

  { "ServerName": "", "Database": "", "UserName": "", "Password": "", "Port": "", "AdvancedSettings": "", "CommandTimeout": "" }

• Oracle

  { "ServerName": "", "Port": "", "InstanceName": "", "Database": "", "UserName": "", "Password": "", "AdvancedSettings": "", "CommandTimeout": "" }

• ODBC

  { "ServerName": "", "Database": "", "Port": "", "UserName": "", "PassWord": "", "DsnName": "", "odbctype": "", "Driver": "", "AdvancedSettings": "", "CommandTimeout": "" }

• Presto

  { "ServerName": "", "Database": "", "Port": "", "UserName": "", "Password": "", "AuthenticationType": "", "AdvancedSettings": "", "CatalogName": "" }

• InfluxDB

  { "ServerName": "", "Database": "", "UserName": "", "Password": "", "Port": "", "AuthenticationType": "", "AdvancedSettings": "", "CommandTimeout": "" }

• SparkSQL

  { "ServerName": "", "Database": "", "Port": "", "UserName": "", "Password": "", "AuthenticationType": "", "AdvancedSettings": "" }

• SnowFlake

  { "ServerName": "", "Database": "", "UserName": "", "Password": "", "AdvancedSettings": "", "CommandTimeout": "" }

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.

   

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

   

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.

   

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

   

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.

   

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.

   

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

   

   

   You will receive the following highlighted 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.

   

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