Forum Discussion
Issue with setting connection with embedded Power BI c#
glennbrodie wrote:
We have muti tenant DB, with PowerBI Embedded - in order to run the report for each tenant, my uderstanding is we have to clone the report, then set the connection string. When we do this, the connection string does not change, but we receive no errors - see code below:
CloneReportRequest cloneReportRequest = new CloneReportRequest()
{
Name = $"{newReportName}-{Host}"
};
report = client.Reports.CloneReportInGroupAsync(groupID, report.Id, cloneReportRequest).Result;
var dsnArray = hostDataRepository.Get(Host).DSN.Split(':')[1].Split(';');
var datasource = dsnArray[0];
var initialCatalog = dsnArray[3].Split('=')[1];
ConnectionDetails connectionDetails = new ConnectionDetails()
{
ConnectionString = $"data source={datasource};initial catalog={initialCatalog}; persist security info=False"
};
var setConnections = client.Datasets.SetAllDatasetConnectionsInGroupAsync(groupID, report.DatasetId, connectionDetails).Result;
- How do you identify that the connection string is not changed, by calling the Get Datasources?
- It is only supported to change the connection strings of the datasets in DirectQuery mode, what is going on when calling the Set All Connections instead of the C# SDK in Postman?
So it appears the issue is more complicated - it turns out the data connection is changing but it apparently takes a bit of time to see. However, the issue is that when you clone the report, it uses the same data set that is in the original report for the resulting report. So when you change the data connection for the resulting report, you are changing it for all the reports that you copied for each tenant from the base report. This is not the desire result - we want to clone the report with a clone of the data set so that when we change the connection for the report it is unique to that report. The high level is that we are trying to create reports for every tenant (becuase we cant change the connection uniquely on the fly), and each tenant has their own Database. Is there a better approach to this problem? Right now we are stuck with manually copying every report and manually setting all the data set/connections - not a good solution at all.