One DB, Multiple Environments.

[sm_talha]

Hello Guys, 

I am in a strange conditon that, I have one SQL DB, from where I am pulling data to dataflows in three environments (dev,test and prod) on Power BI Service. I need suggestions what should I do because everytime I promote a data model for example from dev to test, I have to go to the power query of dev data model and change each table's data source to test dataflow and then save and publish the data model to the test environment. 

Should I keep dataflows in only one environment and connect data models in all environments to that one? is it a good practice? or is there any other sufficient and time efficient method? 

Please put your suggestions, I'd really appreciate your help. Thank you.    

[v-angzheng-msft]

Hi, @sm_talha 

Here are some references that may be helpful:

Power BI Dataflows Tutorial and Best Practices [Full Course]

What you’ll learn:

✔️ How to build re-usable, scalable ETL work in the Power BI Service

✔️ Learn how Power BI Dataflows can support your team and enterprise BI goals

✔️ To understand the role of the Common Data Model and integration with other Azure Data Services, including Azure Data Lake Gen2

How to deploy dataflow from UAT workspace to production workspace

Move dataflows across workspaces with the Power BI REST API

Best Regards,
Community Support Team _ Zeon Zheng
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.