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

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

[ad_1]

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

That is the second a part of the collection of weblog posts displaying the best way to combine Energy BI with Azure DevOps, a cloud platform for software program growth. The earlier publish gave a quick historical past of supply management programs, which assist builders handle code modifications. 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 the best way to combine Energy BI (Cloth) Service with Azure DevOps.

This weblog publish explains the best way 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 Undertaking is and the way we are able to create it.

Energy BI Undertaking (*.PBIP) is a brand new file format for Energy BI Desktop that was introduced in Could 2023 and made accessible for public preview in June 2023. It permits us to save lots of our work as a mission, 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 programs, comparable to Git, to trace modifications, examine revisions, resolve conflicts, and evaluate modifications. It additionally permits us to make use of textual content editors, comparable 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 modifications 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 programs, textual content editors, and CI/CD programs troublesome. 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 penning this weblog publish, we now have to allow it from the Energy BI Desktop Choices and Settings.

Allow Energy BI Undertaking (Developer Mode) (Presently in Preview)

As talked about, we first have to allow the Energy BI Undertaking (Developer Mode) characteristic, launched for public preview within the June 2023 launch of Energy BI Desktop. Energy BI Undertaking information permit us to save lots of 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 elements of our Energy BI file, comparable to information sources, queries, information mannequin, visuals, and many others.
  • Use any textual content editor or IDE to edit our Energy BI file
  • Evaluate and merge modifications
  • Collaborate with different builders on the identical Energy BI file

To allow Energy BI Undertaking (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 Undertaking information
  3. Click on OK
Enabling Power BI Project (.PBIP) save option in Power BI Desktop
Enabling Energy BI Undertaking (.PBIP) save possibility in Energy BI Desktop

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

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

To clone a Git repo on a neighborhood 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.

Notice

Whatever the desired cloning methodology, we now have to put in Git on the native machine.

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

  1. In your internet browser, navigate to your Azure DevOps Group utilizing this sample: https://dev.azure.com/{your_organization_name}
  2. Click on the specified Undertaking
Navigating to Azure DevOps Organization and Project
Navigating to Azure DevOps Group and Undertaking
  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 Enable an extension to open this URL; click on the Open button
Allow an extension to open Azure DevOps Repo URL in VS Code
Enable 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 carried out now. You may click on both the Open button to navigate to the chosen cloned repo inside 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

To this point, we now have cloned an Azure DevOps repo with VS Code. The subsequent step is to create a Energy BI Undertaking.

Create a Energy BI Undertaking

The subsequent step is to create a Energy BI Undertaking utilizing Energy BI Desktop. You may both create a brand new mission from scratch or convert an present PBIX file right into a Energy BI Undertaking file (PBIP). On this weblog publish, I create a brand new file from scratch.

To create a Energy BI Undertaking 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 gadget

Notice

You might wish to save the mission in your OneDrive. In that case choose the OneDrive possibility on the Save as menu.

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

Once we navigate to the situation the place we saved the mission, 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 may discover and edit these folders and information utilizing Energy BI Desktop or some other instrument of your selection comparable to Tabular Editor or perhaps a notepad editor comparable to Notepad++.

Now that we created the Energy BI mission, let’s stick with it and create a easy information mannequin and report.
Since that is only a easy take a look at, we are able to hook up with any information supply of selection, 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 modifications regionally 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 modifications
  2. To commit the modifications we enter a remark that explains what we now have carried out
  3. Click on the Commit button to commit the modifications to Azure DevOps Repo
Committing the changes on our local machine in VS Code
Committing the modifications on our native machine in VS Code

Relying in your VS Code settings, you could get the next message on VS Code saying “There are not any staged modifications to commit. Would you wish to stage all of your modifications and commit them immediately?” as proven within the following picture. This query asks you if you want to Stage all modifications first, after which Commit them regionally. Be taught extra about Staging modifications 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 modifications and commit them immediately

To this point, we dedicated modifications to our native machine, we now wish to publish the modifications 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 modifications to the Azure DevOps repo. The subsequent step is to examine the DevOps repo. Checking if the modifications have gone by way of on Azure DevOps is simple. We simply have to navigate to the specified Undertaking on Azure DevOps.

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

Log into Cloth and navigate to the specified Workspace. If you happen to appropriately 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 Cloth 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 really working.

Running the synchronised report Azure DevOps on Fabric
Operating the synchronised report Azure DevOps on Cloth

As you may see, the report is empty. It’s because the Git integration in Cloth solely synchronises the dataset and report definitions, not the info. Due to this fact, we now have to both refresh the dataset or Publish the report back to Cloth from Energy BI Desktop.

Notice

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

That is it for this weblog publish.
Within the subsequent weblog, we take a look at some real-world working eventualities and talk about present limitations and concerns.
So keep tuned for that.

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

[ad_2]

LEAVE A REPLY

Please enter your comment!
Please enter your name here