Change Workspace from DEV->QA-PROD in Deployment Pipelines for Power BI Dashboard

[cmkp2675]

Hi Everyone,

I published my Power BI dashboard to my fabric_dev env. I need my Datasources should change automatically from deployment to QA and QA to Prod It should pick the Datasources automatically without any manual intervention. Give me step-by-step instructions more granular and also include where can I get those information in fabric.

[suparnababu8 · Accepted solution]

Hi @cmkp2675 

You can achieve this by using Autobinding and parameters concept.  

You have to create parameters as per your data source in Power query editor. later you can publish into dev workspace and deploy to QA. Once deployment completed then click on rules of workspace(one time step) and change the data source to QA. then repet the same for QA to PROD also. 

now you can begin the deployemnet from DEV to QA . once deployment succeded you have to refresh the semantic model to view latest data in each stage. The same process am follwing in my project.

Below URLs might helps you. Please go through it.

Create deployment rules for Fabric's ALM - Microsoft Fabric | Microsoft Learn

The Microsoft Fabric deployment pipelines process - Microsoft Fabric | Microsoft Learn

Did I answer your question? Mark my post as a solution!

Proud to be a Super User!

[v-kpoloju-msft · Accepted solution]

Hi @cmkp2675,

Thank you for reaching out to the Microsoft Fabric Community Forum. The solutions provided by the super user @suparnababu8, are valid and correct according to the thread. And, I have identified few alternative workarounds that may help resolve the issue. Please follow these steps:

Set Up Separate Data Sources for Each Environment: In Power Query Editor, configure distinct connections for your data sources to point to different environments (DEV, QA, PROD). Instead of using parameters, directly set the connection strings for each environment within separate queries. Utilize different data source credentials and URLs for each environment. This necessitates maintaining distinct data sources for DEV, QA, and PROD in your Power BI or Fabric workspaces.

Create Multiple Workspaces: Establish separate workspaces in Fabric for each environment (DEV, QA, PROD). Ensure that the datasets and reports in each environment are linked to the appropriate data sources configured in step 1. This enables each workspace to have its own environment-specific data sources, avoiding conflicts during deployment transitions.

Use Dataflows for Centralized Data Management: Rather than relying solely on Power Query inside the report, use Dataflows in Microsoft Fabric to centralize data source configuration. In Dataflows, define separate data sources for each environment and use the same Power BI reports across environments. This method ensures environment-specific backend data management and automates transitions without parameter changes.

Automate Environment Switching via Workspace Configuration: Set up workspace-specific parameters that automatically adjust when deploying from DEV to QA to PROD. These parameters can map the workspace connection string or environment-specific data source automatically.

Refresh the Data Model: After deployment, refresh the datasets to ensure that data from the new environment (QA or PROD) is correctly populated. This can be done automatically via the Power BI Service or Fabric's refresh capabilities.

If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.

Thank you for using Microsoft Community Forum.

[v-kpoloju-msft]

Hi @cmkp2675,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[v-kpoloju-msft]

Hi @cmkp2675,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.

[v-kpoloju-msft]

Hi @cmkp2675,

I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please Accept it as a solution and give it a 'Kudos' so others can find it easily.
Thank you.

[suparnababu8 · Accepted solution]

Hi @cmkp2675 

You can achieve this by using Autobinding and parameters concept.  

You have to create parameters as per your data source in Power query editor. later you can publish into dev workspace and deploy to QA. Once deployment completed then click on rules of workspace(one time step) and change the data source to QA. then repet the same for QA to PROD also. 

now you can begin the deployemnet from DEV to QA . once deployment succeded you have to refresh the semantic model to view latest data in each stage. The same process am follwing in my project.

Below URLs might helps you. Please go through it.

Create deployment rules for Fabric's ALM - Microsoft Fabric | Microsoft Learn

The Microsoft Fabric deployment pipelines process - Microsoft Fabric | Microsoft Learn

Did I answer your question? Mark my post as a solution!

Proud to be a Super User!