Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
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)
Check out the September 2024 Power BI update to learn about new features.
Learn from experts, get hands-on experience, and win awesome prizes.