Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreThe FabCon + SQLCon recap series starts April 14th at 8am Pacific. If you’re tracking where AI is going inside Fabric, this first session is a can't miss. Register now
We are facing an issue where our Power BI report in the Test workspace is connecting to the development SQL Server database instead of the intended test SQL Server database. We deploying report from Development to Test workspace by using the deployment pipeline. We provide the Test datasource detail in deployment rules as well.
Specifically, we suspect that the connection information (including the database name and credentials) might be stored within the Power BI report itself, particularly as we are using DirectQuery mode or Import mode with a gateway.
Could someone advise on how to ensure that the Power BI report correctly connects to the test SQL Server database when we using we are using DirectQuery mode or Import mode for the data load?
Thank you.
Solved! Go to Solution.
Hi @Anonymous
Using the deployment rules should change your data source connexions as long as there are the valid parameters in your PBI file. If it is not correct, I would suggest using the XMLA endpoint to validate that is using a valid data source.
Hi @Anonymous
Using the deployment rules should change your data source connexions as long as there are the valid parameters in your PBI file. If it is not correct, I would suggest using the XMLA endpoint to validate that is using a valid data source.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 29 | |
| 23 | |
| 17 | |
| 16 | |
| 14 |