Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code FABINSIDER for a $400 discount.
Register nowThe Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.
Solved! Go to Solution.
If it's the same API just running on a different server then yes, you should just need to change the url in the source without re-building your reports from scratch. The other thing I've done in the past is to ask IT to setup a DNS alias for the system so you can point at https://our-erp/api or something like that instead of pointing at a specific server name. Then if you move servers again in future you just need to get the alias re-pointed and you don't need to change any reports. (we also took this approach with our report server instance so that we could upgrade that in future without breaking end user bookmarks)
If it's the same API just running on a different server then yes, you should just need to change the url in the source without re-building your reports from scratch. The other thing I've done in the past is to ask IT to setup a DNS alias for the system so you can point at https://our-erp/api or something like that instead of pointing at a specific server name. Then if you move servers again in future you just need to get the alias re-pointed and you don't need to change any reports. (we also took this approach with our report server instance so that we could upgrade that in future without breaking end user bookmarks)
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Check out the February 2025 Power BI update to learn about new features.
User | Count |
---|---|
10 | |
4 | |
4 | |
2 | |
1 |
User | Count |
---|---|
15 | |
10 | |
6 | |
5 | |
4 |