Home Business Intelligence Integrating Energy BI with Azure DevOps (Git), half 2: Native Machine Integration

Integrating Energy BI with Azure DevOps (Git), half 2: Native Machine Integration

Integrating Energy BI with Azure DevOps (Git), half 2: Native Machine Integration


Integrating Power BI with Azure DevOps (Git), part 2: Local Machine Integration

That is the second a part of the collection of weblog posts exhibiting tips on how to combine Energy BI with Azure DevOps, a cloud platform for software program growth. The earlier put up gave a short historical past of supply management techniques, which assist builders handle code adjustments. It additionally defined what Git is, a quick and versatile distributed supply management system, and why it’s helpful. It launched the preliminary configurations required in Azure DevOps and defined tips on how to combine Energy BI (Material) Service with Azure DevOps.

This weblog put up explains tips on how to synchronise an Azure DevOps repository together with your native machine to combine your Energy BI Tasks with Azure DevOps. Earlier than we begin, we have to know what a Energy BI Venture is and the way we are able to create it.

Energy BI Venture (*.PBIP) is a brand new file format for Energy BI Desktop that was introduced in Might 2023 and made obtainable for public preview in June 2023. It permits us to avoid wasting our work as a venture, which consists of a folder construction containing particular person textual content information that outline the report and dataset artefacts. This permits us to make use of supply management techniques, equivalent to Git, to trace adjustments, evaluate revisions, resolve conflicts, and evaluation adjustments. It additionally allows us to make use of textual content editors, equivalent to Visible Studio Code, to edit the artefact definitions extra productively and programmatically. Moreover, it helps CI/CD (steady integration and steady supply), the place we submit adjustments to a collection of high quality gates earlier than making use of them to the manufacturing system.

PBIP information differ from the common Energy BI Desktop information (PBIX), which retailer the report and dataset artefacts as a single binary file. This made integrating with supply management techniques, textual content editors, and CI/CD techniques tough. PBIP goals to beat these limitations and supply a extra developer-friendly expertise for Energy BI Desktop customers.

Since this characteristic continues to be in public preview when scripting this weblog put up, we’ve got to allow it from the Energy BI Desktop Choices and Settings.

Allow Energy BI Venture (Developer Mode) (At present in Preview)

As talked about, we first must allow the Energy BI Venture (Developer Mode) characteristic, launched for public preview within the June 2023 launch of Energy BI Desktop. Energy BI Venture information enable us to avoid wasting our Energy BI information as *.PBIP information deconstruct the legacy Energy BI report information (*.PBIX) into well-organised folders and information.
With this characteristic, we are able to:

  • Edit particular person parts of our Energy BI file, equivalent to information sources, queries, information mannequin, visuals, and so on.
  • Use any textual content editor or IDE to edit our Energy BI file
  • Evaluate and merge adjustments
  • Collaborate with different builders on the identical Energy BI file

To allow Energy BI Venture (Developer Mode), comply with these steps in Energy BI Desktop:

  1. Go to File
  2. Click on Choices and settings
  3. Click on Choices
Power BI Desktop options
Energy BI Desktop choices
  1. Within the Choices dialog field, go to Preview options
  2. Test the field subsequent to Energy BI Venture information
  3. Click on OK
Enabling Power BI Project (.PBIP) save option in Power BI Desktop
Enabling Energy BI Venture (.PBIP) save possibility in Energy BI Desktop

After making use of the adjustments, we have to restart the Energy BI Desktop.

The first put up of this collection defined tips on how to create a brand new Organisation, Venture, and Repo in Azure DevOps. So, we don’t repeat these steps right here. As an alternative, this part explains tips on how to clone our Git repository created on Azure DevOps on the native machine. Cloning is the method of copying a distant repository to an area machine in order that we are able to work on the venture offline.

To clone a Git repo on an area machine, we require both to put in Visible Studio or Visible Studio Code (VS Code) on the native machine. We are able to additionally use Git Command Line for cloning. The latter is out of the scope of this weblog, so we concentrate on utilizing the VS Code strategies.


Whatever the desired cloning methodology, we’ve got to put in Git on the native machine.

Observe these steps to shut Azure DevOps Repos with VS Code:

  1. In your net browser, navigate to your Azure DevOps Group utilizing this sample: https://dev.azure.com/{your_organization_name}
  2. Click on the specified Venture
Navigating to Azure DevOps Organization and Project
Navigating to Azure DevOps Group and Venture
  1. Click on Repos
  2. Click on the Clone button
  3. From the Clone Repository pane, click on the Clone in VS Code button
  4. Click on the Open button
Cloning Azure DevOps Repos in VS Code
Cloning Azure DevOps Repos in VS Code
  1. Now you get a message on VS Code to Permit an extension to open this URL; click on the Open button
Allow an extension to open Azure DevOps Repo URL in VS Code
Permit an extension to open Azure DevOps Repo URL in VS Code
  1. Choose a Folder to clone information
  2. Click on the Choose as Repository Vacation spot button
Select a Folder as Repository Destination
Choose a Folder as Repository Vacation spot
  1. Cross your credentials on the Git Credential Supervisor and click on the Check in button
Pass Credentials on the Git Credential Manager
Cross Credentials on the Git Credential Supervisor

We’re accomplished now. You possibly can click on both the Open button to navigate to the chosen cloned repo throughout the VS Code or click on the Open in New Window button to open a brand new occasion of VS Code and navigate to the cloned repo.

Open the Cloned Azure DevOps Repo in VS Code
Open the Cloned Azure DevOps Repo in VS Code

Up to now, we’ve got cloned an Azure DevOps repo with VS Code. The subsequent step is to create a Energy BI Venture.

Create a Energy BI Venture

The subsequent step is to create a Energy BI Venture utilizing Energy BI Desktop. You possibly can both create a brand new venture from scratch or convert an present PBIX file right into a Energy BI Venture file (PBIP). On this weblog put up, I create a brand new file from scratch.

To create a Energy BI Venture file, comply with these steps:

  1. Open a brand new occasion of Energy BI Desktop, then click on the File menu
  2. Click on the Save as possibility
  3. Click on the Browse this machine


Chances are you’ll wish to save the venture in your OneDrive. In that case choose the OneDrive possibility on the Save as menu.

  1. Within the Save As dialog field, select the placement of the cloned Azure DevOps repo
  2. Kind in a reputation to your file
  3. Within the Save as sort drop-down record, choose the Energy BI Venture information (*.pbip) possibility
  4. Click on Save
Creating a Power BI Project from scratch in Power BI Desktop
Making a Energy BI Venture from scratch in Energy BI Desktop

After we navigate to the placement the place we saved the venture, we are going to see that the folder comprises the next:

  • The PBIP From Scratch.pbip file
  • A PBIP From Scratch.Dataset folder
  • A PBIP From Scratch.Report folder

You possibly can discover and edit these folders and information utilizing Energy BI Desktop or every other device of your alternative equivalent to Tabular Editor or perhaps a notepad editor equivalent to Notepad++.

Now that we created the Energy BI venture, let’s keep on and create a easy information mannequin and report.
Since that is only a easy check, we are able to hook up with any information supply of alternative, I exploit Microsoft’s SQL Server pattern database: AdventureWorks2022DW.
In my pattern, I get information from the next tables:

  • DimDate
  • DimProduct
  • FactInternetSales

I additionally created a brand new measure as under:

Gross sales = SUM(FactInternetSales[SalesAmount])

Then I created a easy report with a slicer and a line chart as follows, and I saved the adjustments domestically on my machine:

A Sample Report in Power BI Desktop to Test Integration with Azure DevOps
A Pattern Report in Energy BI Desktop

Now on VS Code:

  1. The Supply Management pane detected a few adjustments
  2. To commit the adjustments we enter a remark that explains what we’ve got accomplished
  3. Click on the Commit button to commit the adjustments to Azure DevOps Repo
Committing the changes on our local machine in VS Code
Committing the adjustments on our native machine in VS Code

Relying in your VS Code settings, it’s possible you’ll get the next message on VS Code saying “There are not any staged adjustments to commit. Would you wish to stage all of your adjustments and commit them straight?” as proven within the following picture. This query asks you if you need to Stage all adjustments first, after which Commit them domestically. Study extra about Staging adjustments and Committing right here.

I choose At all times as I don’t need VS Code to ask the identical query once more sooner or later.

There are no staged changes to commit. Would you like to stage all your changes and commit them directly
Stage all of your adjustments and commit them straight

Up to now, we dedicated adjustments to our native machine, we now wish to publish the adjustments to Azure DevOps.

  1. Kind in a remark
  2. Click on the Publish Department button
Publishing Branch in VS Code after Commit
Publishing Department in VS Code after Commit

Now, we efficiently Pushed all adjustments to the Azure DevOps repo. The subsequent step is to verify the DevOps repo. Checking if the adjustments have gone by on Azure DevOps is simple. We simply must navigate to the specified Venture on Azure DevOps.

Changes successfully pushed to Azure DevOps repo
Modifications efficiently pushed to Azure DevOps repo

Log into Material and navigate to the specified Workspace. In the event you accurately configured Git Integration from the Workspace Settings, it’s best to see that the Workspace contents synchronised with the Azure DevOps repo.

Check Fabric Workspaces for Synching with Azure DevOps
Test Material Workspaces for Synching with Azure DevOps

As you see, in my case, the synchronisation was profitable. Now, let’s open the report and see whether it is truly working.

Running the synchronised report Azure DevOps on Fabric
Working the synchronised report Azure DevOps on Material

As you may see, the report is empty. It’s because the Git integration in Material solely synchronises the dataset and report definitions, not the information. Subsequently, we’ve got to both refresh the dataset or Publish the report back to Material from Energy BI Desktop.


Since we work on a Energy BI Venture, when you use older variations of Energy BI Desktop than the Aug 2023 launch, the Publish button is disabled.

That is it for this weblog put up.
Within the subsequent weblog, we take a look at some real-world working situations and focus on present limitations and concerns.
So keep tuned for that.

As at all times, I’d like to know your opinion and ideas. So please share with us what you suppose within the feedback part under.



Please enter your comment!
Please enter your name here