Power BI reports in Process Mining overview
The rebind method you choose depends on whether the two processes you have are using two different workspaces or the same workspace.
The articles in this section use fictitious names. These names are for demonstration purposes and you should use names that suit your preferences. As you go through the procedures, select your own environments and workspaces that correspond to these references.
- Dev environment: Environment from which you want to migrate process mining artifacts.
- Test environment: Environment to which you want to migrate process mining artifacts.
- WkSpace A: Custom Power BI workspace associated with the Dev environment from which you want to migrate the Power BI report.
- WkSpace B: Custom Power BI workspace associated with the Test environment to which you want to migrate the Power BI report.
- Report A: Name of the Power BI report for the process in Dev environment.
- Report B: Name of the Power BI report for the process in Test environment.
Note
Typically, you perform ALM for the Power BI report after you have performed ALM for the other resources of the process using solutions.
The procedures in the Migrate customized Process Mining Power BI reports section assume you completed the following tasks:
You attached a Power BI workspace to your process in your Dev environment.
You performed ALM on other process mining artifacts using solutions.
You made the Power BI report customizations that you want to migrate. If you didn't do this task, do the following steps:
- Navigate to the report page of your process in Power Automate.
- From the command bar, select Open in Power BI.
- Make the changes you want to migrate and save and publish the report.
You can transfer the Power BI reports in three ways:
- Rebind without a using a composite model
- Rebind using a composite model
- Use Power BI pipelines and rebind