Power BI & EDITable deployment pipelines
Last updated
Last updated
We will now create a pipeline in both Power BI and EDITable, and walk through the entire deployment process from beginning to end.
In this section, we will deploy the report in stages to the same destination. This can be useful when you want to maintain version control for your EDITable visuals before sharing the final version of your content with business users across the organization.
The first step is to set up a Power BI pipeline. You can refer to this page to get started.
After creating a pipeline, you can assign workspaces to each stage, i.e., the Development/Test/Production stages of the deployment pipeline. Learn more about assigning workspaces.
Let us assume you have a Power BI report with an EDITABLE visual that you want to deploy in stages. Publish it to the workspace mapped to the first stage (development) of the pipeline.
For this demonstration, we have created a report named 'Employee_Table' and uploaded it under the Inforiver - Pipeline - Dev workspace.
Go to the Deployment Pipelines tab and select the required pipeline that you created in step 1.
From the first stage, select the report and its corresponding semantic model to be deployed to the test environment. Learn more about deploying reports.
Review the items that are being deployed and click on the Deploy button.
After the deployment is complete, you will be able to see the report and the semantic model in the next stage. In this case, it is the Inforiver - Pipeline - Test workspace.
Similarly, after the testing stage, you can deploy the report and its semantic model to the production environment using steps 4 and 5. You can refer to the GIF below.
When deploying reports, please ensure to deploy their corresponding semantic models.
In the EDITable workspace, go to Utility > Pipeline. Click on Add Pipeline.
Click on Add Stage and you can start adding the required stages — Dev, Test and Prod.
Click on Add Report.
A pop-up appears as shown below, based on the number of stages created.
The report IDs can be copied from the address bar of the respective workspaces.
Enter the relevant report IDs of the reports. Click Next.
A pop-up window appears, displaying a list of all EDITABLE visuals (tables) included in the selected report.
Our report contains only one visual/table, 'EmployeeDemo'. Click Add to add this report and create an EDITable pipeline.
Note: In this example, we have deployed the reports to the same destination (Azure SQL) for simplicity. The next section will explain how to configure different deployment destinations.
A report can also include multiple tables/visuals, one on each page, which can be added to or removed from a pipeline during deployment. You can refer to the image below, where the report has multiple EDITable visuals.
To deploy a report from one stage to another, such as 'Dev' to 'Test' or 'Test' to 'Prod', click the Deploy button next to the report you want to deploy.
Select the next stage for deploying the visual from the dropdown menu.
Click Deploy.
The report is now deployed from 'Dev' to 'Test' stage. Similarly, after testing, you can deploy the report from the 'Test' to the 'Prod' stage by following steps 8, 9, and 10.
In the next section, we will look at the steps to deploy the report to different destinations.
