Power BI Version Control using GIT and Azure DevOps by taik18

hello and welcome to tech18 I'm Amit Adnan and in this video we are going to discuss about power bi integration with Git so we can make use of the git plus power bi for aggression controlling in the previous video we discussed about how we can integrate with fabric and the gate but today we are going to cover with addition of that how we can also use power bi desktop to use that functionality if you are new to this Channel or if you haven't subscribed yet just click on the Subscribe button and also press the Bell icon to get the latest notifications now let's get started all right so there are few things which we may require in order to work on these changes so first of all we need to have Azure devops with Git as a kind of project repository which we need to create I have covered the basic things on my previous video you can go through that as well but if you want to go in detail about how these things work then I also added the link of these things Azure devops and the gate from Microsoft documentation you can also check out that not only that you can also refer to the other videos from other YouTube videos or any other documentation so first of all we need to create a mind repository as a kind of project inside the Azure devops gate and then we need to create the main workspace which we can create in fabric so in the fabric we can create as a for example Finance Dev Finance test and finance prod so this is basically we can make use of the deployment pipeline so the version controlling is a another thing so the version controlling is another thing and the deployment pipeline is also another thing so machine controlling helps in terms of the developers who want to make the changes to the report add a measure add a table add a visualization or any kind of modification which you required so the same thing it has to apply to the test so that the small group of people can test it out and give the green signal not only that it can also help for the final production deployment once they approved in the testing environment so this is how the deployment pipeline works and next thing what we need to do here is we need to create another workspace for each developer so the developer continues the my workspace that is for their own purpose but for officially it is good to create a separate workspace for each developer so it can be synced between the workspace for the developer to the development workspace of our real domain workspace so think in the sense they can publish the data from this workspace to that workspace using the git integration so that's how it will work so these are the things which we covered in our previous video and once the developer make the changes on this workspace then they can use this pull request so that it can publish into this workspace and from there it can take it further on this direction finally this will also sync between these two Azure devops here and if the user want to redo again they need to create a brand so that we can get the data from this to this workspace this is what we discussed previously and every pull request and the commit we are going to delete the branch but here is a slight change so you can follow what your company policy has but for easy access purpose what I prefer here is instead of going through the deleting of the branch we just need to create a branch for each developer and we can keep this forever we can reuse those brand changes here so now as a first step let's go to this our previous video the workspace which we had created here is this one right the four cells 2 is 1 and then we created this test and production this is for the development and this is for the testing and this is for the production which we use for deployment pipeline but there is one more workspace here WS2 for development 2 is for developer 2. so this is the workspace which you are going to use as a sequence of this video so if you go inside to this one right now we have just only one report which is food sales so there are a couple of things which we need to do now so the first thing is this is the report which is published on power BS service using upload method last time and also I make the changes directly on the power of your service now the thing is we need to create a file using power bi desktop and then we need to publish this report onto this workspace right so this is how it is but there are two things one is directly we make the changes and publish to the workspace another thing is we can make use of Visual Studio code that is the vs code we used to call so it's a kind of lightweight tool and it has a lot of functionality inside to that we can connect to our Azure devops to this repository on the vs code and from there we can sync it to our local Drive using this one and in the local drive we can have the project power View files coming from this git repository to our local drive and also we can save our power bi desktop file as a project file so pvip and you can also save it directly onto our local drive and from this local Drive we need to sync it to this workspace basically it will go to Our Brands actually it will go to the Azure devops that will sync to our work Branch but in short it will just going to be synced between this workspace and from here it will go to this development workspace and again so on so that's how the sequence of process will work but I will show you here first of all let me open a power via desktop so that uh we can directly publish into the workspace any report and also we will take an example of how we can configure to the vs code but I think while this is working on let me open vs code this is a lightweight tool I will also add a description of this on our video so that you can have a look into that all right right now you see it is already connected to this um project if I go back again to power bi service and Azure devops here you see we have this fabric lm01 this is the kind of folder which is connected here inside to this project and also we have another thing which is YouTube demo 2 and if I click inside to this one we have just one report inside here right so how we can able to create that so first of all we need to create here this is the one and if you click on this three dot option we have here the Clone option so we can clone this one inside to our vs core but before that as being a developer Now by myself we need to create a branch so every changes we should not have to directly make the changes to the main one it has to be through branch and from Branch if everything goes well then we need to merge it into the main branch so if you click on the branches now and this is the main and this that file added so I will create a new branch and here this will ask based on what so I am need to use it from the main branch and here this can be for developer 2. Branch developer 2 and if you want to add to your any task so that's the advantage of using Azure devops I can click on create so this is the one branch here now you can click on this branch and here you have options that are Bill and clone you just need to click on the Clone option here and then here you have option to copy the link and you can use it inside to your vs code or you have direct option here clone in vs code if I click on to this one we have multiple options here visual studio and webstorm kind of thing but as we are going to use vs code I click on the vs code here so it is asking me to open it here yeah it I want to open it here and git wants to open the URL yeah open this one and it is asking for me to where we need to store it as a local thing here like I mentioned here we need to set up here at the local drive right so we just need to go to our setting here which is I would like to go here for GitHub and I will right click here just create a folder YouTube demo to and then I will select as a repository destination so what will happen now if I go to that particular folder plan for GitHub and YouTube demo too this is actually going to create those projects and store it over here so you would like to open the closed reposit clone repository or current workplace you want to open it here or a new one I prefer to be opening a new one because it will be clear for you to understand it is opening up here now I can see these two folders added here so let me refresh this one so YouTube demo 2 it is added type LM which is one project and if I go inside to this one it has added two different folders one is Fabric lm01 and another is YouTube two so and inside YouTube two you can see only one report that is actually synced between the workspace in power BS service so the same thing which is also happened here as well so that's a good thing now if we go back to the workspace and then on the workspace setting we can see it here the git integration if you see here it is actually connected to one of the development to Branch one so which is this one we used previously but this time I would like to click on this one so you have option to switch and overwrite yeah you can switch and override I will click on this one this is going to switch and sync the files between casual devops kit to here on the workspace now you also see the status which is showing up here as sync so that is clear now so we have now sync between the workspace we have also added to our vs code here now if I open up any one report for example so you also need to log into your account I have logged in here at tech18.com and I can directly publish it from for beta stock to power bi service without creating any project so this is the Home tab we have a three tab basically here and this one is the home one and if I click on publish here so make the changes so yes and one more thing which I want to highlight here uh I need to publish into the dev2 workspace because being a developer to on it publish only on to this workspace so click on select this will publish over there so what I was saying is like once you use the version controlling it's just going to upload and sync between here and there the devops and power bi and your local everything is the metadata it will not going to transfer you the real data so you also need to make sure when you do this kind of process you need to refresh again in power Base Service but in usual way when we publish here from desktop to power Base Service it actually loads the data as well but if you're going through the visual studio code process it is actually not so you need to make sure you refresh it again over there so now if I go back to Power BS service and if I refresh this browser what we see now is another report added and also it is giving me a message here as uncommitted if I come back here to visual studio code and hit refresh right it is not giving me any information here about is there any changes over there or not because it is power pay desktop it is loaded to our workspace and it is not actually synced to the branch so that's why there is no information happens here on the vs code so the next thing what we need to do on the right side we have a source control option which is showing an indicator of Red 2 it means if you click on this one it has a changes and update if there is a new changes from this workspace then it will comes under these changes if there is an update from the branch you need to sync between to this workspace then it will come under the updates here so I will just make a commit message it is necessary to add a commit message so that you can understand in future what make the changes what the changes you have make you have made so added report Us sales analysis right so you need to make sure to take off these two options because if you are working on some report but you don't want to sync for now then you can skip that for now I'm okay with these two click on Commit here so now you see you your selected changes uh were committed and there is no pending here you don't have any changes any uncommitted changes will be listed here all right so this is also now showing at the git status to be synced here that's it now if we go to this one and hit refresh it is not giving me anything here um okay now if we go back to this repository and then click on the file here also you will not see the new changes because the new changes are still not sync between this to the main one and if I click on the branches again so let me load this one new updated Brands too just now so it is just giving me the message here we have an updated Branch here so for this we need to click on create pull request so we need to pull this request so that it can sync to the main branch so I will click on the create a pull request and the same message it will carry forward here and click on create and we need to give the approval this is kind of separate process flow you can go and learn about this data and devops and click on complete so here previous video I use this option to delete Brands to after matching so I just uncheck here from this video because I want to reuse the same brands and complete mirrors here so now this is going to merge the branch data into the main branch so that it can also be available on to our main workspace which is development workspace so I miss that actually if I click on this one development workspace which is this one and it should not have any report here yeah you're right right so basically so right now this is Mets completed so completed the pull request test now okay and when we go to this main workspace which is used in the deployment pipeline it is giving me message here we have a pending sync changes here but before that let's go back and refresh here so still it is not showing any information here okay that's totally fine and if I go inside here also we don't see anything here all right so first of all we need to publish it here and the source control here also giving me messages here we have an update too because it is now coming from Azure devops to this workspace so I'll select both of them there is no other option you need to do that and click on update on now this will sync from the main branch from the main actually main repository to this main workspace of our development workspace and from here we can take it further to use the deployment pipeline to deploy into the testing workspace and then to the Protection One all right so now you see this is also has sync between these things so if I come back here and refresh again is changed actually why it is not giving me the refresh option and if I click on the branch it will sync this one and it is actually giving me a message now actually I need to click on this option which is the source control and here it is giving me like Alm 18 gate main there is a two sync option Printing and also the arrow which you see here it is actually want us to sync to the local from this service from the main one so this action will pull and push commit from the origin main so it is syncing from the main to this or local one yeah okay all right now if we go to this folder as state here Us sales analysis data set and Report yeah as mentioned earlier so usually Power by desktop file will have only one file but using the Version Control it will split into two different files one is data set another is for the report so that is how it is created now so as per our plan so we directly publish this to our workspace and then we sync between this into our workspace and to the development workspace vice versa and from here we have got back again so this process is done so now the next thing is we need to save the file as a power VA project file and then sync between using your Visual Studio code so how can we do that basically so let me click file and open a new one for example this one Adventure was 202301 dot tbip which is I already saved locally but for our reporting purpose let me open up a new file itself so this is the regular report which I usually do for the adventure works for all kind of my YouTube demo majority of them so it is opening the file if you have any questions meanwhile please let me know in the comment section below if it is something is not clear uh if you like this video till now and then if you want me to do further more on these topics please also let me know in the comment section below and if you are new to this Channel or if you haven't subscribed yet just click on the Subscribe button so that it will help me a lot in order to boost my motivation to do further more based on your feedback based on your like and subscription all right this is a sample report which is open up here and first of all we need to go to file and then options and settings and then options and in the preview feature we need to enable powerba project.tbip save option so that is how you can work on that so we need to click on file save as and then click on the browse where you want to save I want to save it on the same folder that's the main thing you if you are using a local repository configuration then you have to use the same folder so I'm using the same folder and also I'm using the same folder inside to that and here I have option to save as which is power PA file pbit template file and project file so you need to click on Project file cbip it will be the extension and then click on Save so once you click on save it will actually this is a folder right so it will actually going to give me options this is saved here let me refresh this yeah so now you see it has Adventure works the same data set and report and also there is a one more file which is pbip so if you want to open the this power BF file you can directly click on this pbif it is going to open up your power beta stuff but for this you need to have a latest Power by desktop and now you may think about for these two things there is no file size so how can we open up that so for this you need to click on the data set I think it's not in the data set if in the report you have this pbir it is basically power bi report definition so we can click on this one it is going to open up in power by desktop you can also make use of that so far clear so now this is the thing then so let's assume that we have made the report and now we are using into our local drive and now let's go to this Visual Studio code so it is going to check on this one and it's giving me a list of things which is available inside to the folder you may think we have used only one report but it is showing up 14 items so it is basically if I go inside to this one it has a multiple files so everything is here so the model that beamed right is actually expanded as a Beam file so you can make use of this Beam file in our table editor to make any changes inside to that so we have a lot of files here so that's why it is showing up here to be like 14 files so we need to commit here so the main thing is we need to commit here um to our Branch repository and also we have to mention the message here now this is showing as control enter to commit on Main but actually we need to connect to the Brands right so if I click on this one it is giving the option here where we need to use this uh actually the origin should be Branch development 2 here I just click on this one option and it is giving me list of option here where create a new Branch create new brands from check out detach and actually I need to click on Branch tab 2. so now this will change actually the link between the local vs vs code to the branch so now it is giving message your commit on the branch to development and then click on Commit so actually I need to give a message so here giving message please enter the commit message so I need to enter a message here added report okay I need to first of all close this one then only it will come here added added report Adventure works and click on Commit so this will now commit from your local to the brands too and then push one commits to origin Brands too so you need to click on this one okay don't show again this is going to origin and the development tool so that's the reason actually in the previous few minutes we haven't seen any changes because it is actually connected to the main branch not to the brands devtools so right now this is sync and the committed to this or we Sorry in the branch if I go to this Azure devops again and click on the branch here it is taking a bit time actually so you updated Branch 2 just now so that's why it is giving message here and click on create full request it is also adding the same message added report Adventure works but before to that right now I'm at the main workspace and you see this is now there is no report added but if I go to this development workspace which is for the developer too and here you should see the another thing here right now this is not available here but first of all you need to sync between that so here this part like if I go back to the presentation the power player does stop making the changes and saving local Drive syncing to this workspace this thing is responsible for the developer here I will just mentioned developer 2 for each understanding so this is the scope of the developer too and this is basically the scope of the main admin I can say because you need to refer admin right yeah so because you need to check whether that things have been completed successfully and then they need to sync between this developer workspace to the development thing so all these things can be responsible by admin or any other who has a well experience on the power via side they can do that so it should be a two different person in my perspective all right so now we need to click on the source control and here it is showing as a development tool branch and click on update all so this is now going to update the things from the development to Brands to this development to workspace is coming up here it is still updating as these are a little bit big files so it is taking a bit time because it has a lot of pages visuals and everything all right it is done very quickly itself so we have other works here and the things here now if I go back here to create a pull request yeah we need to create on the brands pull request and create a pull request once you do so there is no merge conflict it has checked here and we need to click on approve and then complete so here also make sure that you don't delete the branch if you delete the branch then you need to follow then you need to follow the first video which I mentioned every time they need to create a branch sync between the brands and then do these things and then click on complete merge so nurse pull request just now and everything is fine now let's go back to the main workspace which is vs2 and now you see it he's giving me a message that is pending changes click on the source control and it is the main branch and then click on update all yeah it's done now you also see it is a adventure works here and it's everything is synced here now if I open up any one of the report here I may not see any data here because the data is not available it's just the metadata so we need to refresh the data then only it will come up here everything is done so far so this is how the things works so let me quickly try to refresh these things within a kind of one minute period all right so this is the main repository which we have we need to configure into git Azure devops and from that we need to con sync between the main repository to the main development thing only on the development work and then we need to create separate workspace for testing and production which is for the deployment pipeline usage but this development it has to be created for for only for this purpose and another workspaces we need to create for each and every user for each and every developer so that is how it is and then we need to sync this main branch as a brand so we need to create a branch here from this one and this Branch actually has to connect it to this one right in simple term actually it should not be like that it has to be come from this one for example this is the main repository and from this point repository we need to create a branch on this one so once you click on this one the user need to be synced between the local Drive using the vs code to this workspace and they can either directly publish from the Power by desktop to the workspace and then sync in the reverse direction or they can use the save as power via file using the visual studio code and then sync to the workspace and from this workspace it will go to this Visual Studio code and from this we just sort of code it will again sync to this development workspace and then it will follow the testing and production as clear so this is how the sequence works if your anything is not clear I hope I have covered both of the things in the two videos how we can work on the power by desktop also directly on power via service if you have any changes or if you have any issues on that please let me know in the comment section below um I will happy to help you on these things so if you like this video just hit the big thumbs up button if you are new to this Channel or if you haven't subscribed yet just click on the big surprise subscribe button and also press the Bell icon to get the latest notification but make sure you turn on notification on your devices share it with your friends and colleagues if you have any queries and feedback just post it in the comment section below thanks for watching keep learning see you in the next video

Channel: taik18 - Mohammed Adnan

Views: 9,900

Keywords: Power BI Version Control using GIT and Azure DevOps by taik18, Power BI Version Control using GIT and Azure DevOps, power bi, power bi training, power bi version control, power bi version control using git and azure devops by taik18, powerbi, power bi for beginners, power bi version control using git and azure devops, Power BI Version Control using GIT, power bi version control using git, #fabric, #taik18, DevOps, power bi tutorial, GIT, taik18, power bi desktop, power bi dashboard

Id: fWamDXiOmvE

Length: 28min 5sec (1685 seconds)

Published: Sat Sep 23 2023