Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
I have a problem related to changing the location of my server.
On my deskop I connected to an MySQL server, built my report, published to powerbi.com and successfully refreshed using an on premise gateway. The server name was something life xxxxxxxx.rds.amazonaws.com.
A DNS was configured to point to the server and the on premise gateway was updated.
I then opened my pbix file on my desktop, changed the location of my MySQL server from xxxxxxxx.rds.amazonaws.com to the new DNS name, I could connect and refresh locally. Then I published to powerbi.com but now my dataset can not see the gateway.
I created a new report with the DNS and published to powerbi.com and the gateway was found, so the gateway works for a new report but not an existing report with the location changed.
Solved! Go to Solution.
I resolved this, the problem was that I had multiple data sources, one being MySQL and the other being from SharePoint. On the gateway the option for "Allow user's cloud data sources to refresh through this gateway cluster" needed to be ticked. See here for further details https://docs.microsoft.com/en-us/power-bi/service-gateway-mashup-on-premises-cloud
I resolved this, the problem was that I had multiple data sources, one being MySQL and the other being from SharePoint. On the gateway the option for "Allow user's cloud data sources to refresh through this gateway cluster" needed to be ticked. See here for further details https://docs.microsoft.com/en-us/power-bi/service-gateway-mashup-on-premises-cloud
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 55 | |
| 50 | |
| 43 | |
| 16 | |
| 15 |