Migrate using Power BI pipelines and rebinding

This solution involves using Power BI pipelines for moving entities across two different workspaces.

Attach a workspace to your process

1. In the Environments dropdown menu at the top of the screen, select your Test environment.

2. On the navigation pane to the left, select Process mining.

   If your process was newly copied over to the Test environment, there's an exclamation mark inside a speech bubble on the process. This mark indicates that the process was imported.

   

3. Select the process, and then select Confirm.

4. If your process was newly copied to the Test environment, select the process and go to step 5. If the process wasn't newly imported, go to step 6.

5. Select a new workspace for this process:

   1. Select a different workspace that you will be using for the Test environment.

   2. For Report Name, enter a different report name than that of your previous report.

      Important

      The report name must be different from the report name of the process in Dev environment.

   3. Select Continue and continue setting up your process.

      

6. (If your process wasn't newly imported) Attach a custom Power BI workspace to the process:

   1. Go to the process details page for the process.
   2. On the Details card, select Edit.
   3. From the Power BI workspace (optional) dropdown menu, select your WkSpace B Power BI workspace that you want to port changes to.
   4. Provide the different report name than that which you used before.
   5. Select Save > Continue.
   6. From the command bar or in the report view, select Refresh data.

Deploy Power BI reports using pipelines

1. Sign in to Power BI.

2. From the left navigation pane, select Deployment pipelines.

   

3. Create a new Power BI pipeline by following these steps:

   1. Select New pipeline.

   2. In the Pipeline name and Description (optional) fields, enter a name and description.

   3. Select Next.

   4. Customize your stages.

      For this example, we use Dev and Test. If you see others, select the trash can icon next to it.

   

   1. Select Create.

4. Assign workspaces for the pipeline.

   1. For the Dev stage: From the dropdown menu, select your WkSpace A > Assign a workspace.

   2. For the Test stage: From the dropdown menu, select your WkSpace B > Assign a workspace.

      In the following screenshot, your environments might use a different name.

   

   The visual that compares the contents of each workspace now shows.

5. From your ALM A workspace, select Deploy > Deploy.

   

   When deployment is complete, go to your WkSpace B, which contains items copied over from your WkSpace A.

   

Rebind your semantic model

The final step is to rebind the semantic model in the ALM B workspace to the report from the ALM A workspace.

1. Go to your WkSpace B, and then select Report A.

   It's normal to see issues with loading the report.

2. To download the report, from the command bar, select File > Download this file > A copy of your report with a live connection… > Download.

3. After downloading, open the file in Power BI desktop.

4. From the command bar, select Transform data > Data source settings.

5. From the list of semantic models, select the Report B_Dataset_206… semantic model.

6. Select Connect.

   

   The procedure is a success if the report has report customizations from the Report A but uses the semantic model from the original Report B.

7. When you finish, select Save > Publish from the command bar and publish to your WkSpace B.

8. When complete, go to Power BI web and go to your WkSpace B workspace. The new report is now in the workspace. You can also rename it.

9. You can clean up the workspace by deleting the semantic models and reports that you don't need.