Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
I have been using the Rest API to publish PBIX files to PowerBI.com. Part of this process was setting the connection strings to the production instance. I struggled with the documentation, as we are using an on-premise data source with the enterprise gateway.
I spent many hours troubleshooting why i was getting an error
Solved! Go to Solution.
I have been using the Rest API to publish PBIX files to PowerBI.com. Part of this process was setting the connection strings to the production instance. The documentation doesnt say much around using an on-premise data source with the enterprise gateway.
I spent many hours troubleshooting why i was getting this error
The example connectionstring that is used is this:
"data source=MyAzureDB.database.windows.net;initial catalog= Sample2;persist security info=True;encrypt=True;trustservercertificate=False"
I couldnt get that to work, i got it to work using the following format:
"data source=mylocaldbinstance;initial catalog=localdb;persist security info=False" .
Hopefully this helps others who get stuck on this.
I have been using the Rest API to publish PBIX files to PowerBI.com. Part of this process was setting the connection strings to the production instance. The documentation doesnt say much around using an on-premise data source with the enterprise gateway.
I spent many hours troubleshooting why i was getting this error
The example connectionstring that is used is this:
"data source=MyAzureDB.database.windows.net;initial catalog= Sample2;persist security info=True;encrypt=True;trustservercertificate=False"
I couldnt get that to work, i got it to work using the following format:
"data source=mylocaldbinstance;initial catalog=localdb;persist security info=False" .
Hopefully this helps others who get stuck on this.
@williamd wrote:
I have been using the Rest API to publish PBIX files to PowerBI.com. Part of this process was setting the connection strings to the production instance. The documentation doesnt say much around using an on-premise data source with the enterprise gateway.
I spent many hours troubleshooting why i was getting this error
The example connectionstring that is used is this:
"data source=MyAzureDB.database.windows.net;initial catalog= Sample2;persist security info=True;encrypt=True;trustservercertificate=False"
I couldnt get that to work, i got it to work using the following format:
"data source=mylocaldbinstance;initial catalog=localdb;persist security info=False" .
Hopefully this helps others who get stuck on this.
Great to hear you could finally get this to work, was the API Set All Connections called in your case?
Hi,
I am trying the similar thing. Using Import API I have imported set of PBIX files to PBI Service. Now I would need to update the connection string for all the imported ones. Connection string varies for different App workspace.
I have been using the Rest API to publish PBIX files to PowerBI.com. Part of this process was setting the connection strings to the production instance. I struggled with the documentation, as we are using an on-premise data source with the enterprise gateway.
I spent many hours troubleshooting why i was getting this error, after following the apery sample:
"data source=MyAzureDB.database.windows.net;initial catalog= Sample2;persist security info=True;encrypt=True;trustservercertificate=False"
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
14 | |
2 | |
2 | |
1 | |
1 |