What is The Best Practice for Developing a Report That Can Be used for Different OData URLs?

[I_NeedMorePower]

Greetings dears!

I'm planning to develop a report that can work for different environments.

My data source is D365 FO and I want to know what is the best practice to deploy a Power BI report for different D365 environemnts in the easiest way (or best practice wise) possible.

The data model is the same everywhere but I want to build a report that I can change the Odata URL easily.

How can I achieve that?

Any advice is appreciated!

Thanks in advance !

[ppm1 · Accepted solution]

Best practice would be to store the URL (or the part that changes) in a parameter and use that in the query. That way you can then save your file as a pbit and share it w/o any data (and the user would be prompted to enter the parameter value when they open it).

Parameters - Power Query | Microsoft Learn

Pat

[I_NeedMorePower]

Hi ppm1,

I just tested what you suggested and it works as per what I needed !

Thank you for your help!!! 🙂

[lbendlin]

Is this an "embedded - app owns data" scenario?  Have you considered service parameters?  You'll run into all sorts of formula firewall issues.

[I_NeedMorePower]

Hi lbendlin,

Thanks for your reply !

I want to embed it in D365 FO. and I want the report to be deployed in multiple D365 FO.

So this is why I want to build a power bi report that can be used in multiple enviornments and deploying the power bi should have no changes if possible.

But after some search it seems I was wrong and I can't use an OData to achive this requirement if I want to embed it in D365 FO Analytics workspaces.

I'm still reading and trying to learn how to do it for D365 FO.