Bulk update of connection string across multiple Power BI workbooks
Our Power BI workbooks connect to Azure Databricks and we recently updated the cluster. We need to update the http path in all the connection strings across all of our workbooks. Is there a way to allow the connection string to be updated once and it update throughout all the workbooks as opposed to changing every single workbook connection string individually?SQL Connection String Format
Hi all, I'm running into a strange issue and wonder if anyone's experienced it. I have several Power BI reports that are importing data from SQL server. The SQL server is Server name/Instance Name and I'm providing the DB name as well. Everything works fine in Power BI Desktop for Report Server, but when I publish to the web portal and try to provide my credentials and I'm getting an error that I cannot connect to SQL. However, I'm able to create the data source in the web portal using the same credentials, if it's in this format: Data Source= Servername/InstanceName; Initial Catalog=DBname But the Power BI reports are in the Format: Servername/instancename;Dbname. Obviously I'm not able to change the Data source on the web portal after the fact. Any ideas?May 2022 version PBIRS changing datasource issue
Hi, we just updated our version and we are now having an error when we promote a report to an environment that has this new version. Power bi reports are not embedding credentials and not changing the connection strings anymore after the version got updated to May 2022. Anyone here know what's going on? this is our first update in 2 years now.. we are getting this error on our deploy: and this on the catalog logs: |ERROR|108|library|Throwing Microsoft.ReportingServices.Diagnostics.Utilities.CatalogItemContentInvalidException: , Microsoft.ReportingServices.Diagnostics.Utilities.CatalogItemContentInvalidException: The item 'Connection strings for reports created with October 2020 or newer with enhanced metadata can only update Live connections. Prior versions can update Live and Direct Query connections.' contains invalid content.;| RequestID = s_6c34a7ae-755e-443d-b09c-d59a0fd8aa25
