Is the git integration with a workspace one-way or two-way?

[pborah]

Right now I have a test workspace synced with a test git repo on devops to push changes from service to git. So the direction is desktop -> service -> git. But as a test case I also pushed a few paginated reports (rdl) to git repo directly from local. However under workspace source control, I don't see any alerts asking me if I'd like to sync those paginated reports.

So my question is, once the direction of sync has been set, git -> workspace or workspace -> git, can't it be changed on an as needed basis? Or is desktop -> service -> git the defacto sync direction for newly created reports whether paginated or powerbi native? 

I understand that once published this direction can go whichever way as needed as changes are made to reports. I'm asking about newly created items that are pushed to a git repo directly fom my local repo without publishing to powerbi first. Thanks. 

Thanks.

[Anonymous]

Hi @pborah 

The files can not be pushed to a git repo from the power bi desktop.

Publish to service is necessary before you pushing the file to the git repo.

Get started with Git integration - Microsoft Fabric | Microsoft Learn

Best Regards

Zhengdong Xu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[pborah]

Thanks @Anonymous , I understand files cannot be pushed to git from within desktop. But nothing is stopping me from saving the project in my local git repo first and then pushing that to git on azure devops, before I publish to powerbi service. So I was wondering how syncronization will look like in such a scenario.

Because at the time of integrating a workspace with git, I'm presented with the option of which way I'd like sync to work - service to git, or git to service. And it seems once you set that, you cannot change it back without disconnecting the workspace first?

[muhssamy]

Yes. Definitely you can do this. Git integration is 2 ways there is 2 tabs in source control one call updates it catches the update on git repo and reflect it to the workspace.

actually workspace is validating the objects comming from git before deployment to the service.

I tried it more than once and it works correctly.

actually also Microsoft recommends pushing pbip projects with TMDL serialization using this method

[fomoisreal]

is there a way to do one-way syncy from Git to PowerBI?

[muhssamy]

what do you want to achieve here ?
and what is the problem of syncing the repo with workspace ?

[pborah]

hi @muhssamy , can you please tell me what exatly you are doing to achieve two-way sync? Because this is my source control screen.

In addition to what has already been synced, I have three additional paginated reports in the repo which are not showing up under source control either under changes or updates. Or are paginated reports not supported right now with the git integration?

For context, I pushed the paginated reports to the DevOps repo first and they are not published in the service yet. I want to pull them to service from DevOps using the git integration. Is this possible? Thanks.

[muhssamy]

it should appear on updates tab if they are commited to your master branch in devops check them on this branch first.

Actually paginated reports are supported as per microsoft documentation here 
Overview of Fabric Git integration - Microsoft Fabric | Microsoft Learn

[pborah]

Thanks @muhssamy , after a bunch of digging around, this is what I found -

https://learn.microsoft.com/en-us/power-bi/paginated-reports/paginated-github-integration?tabs=azure... 

Could this be it? Either way it seems like in order for paginated reports to work with git integration, PBI Service has to be a middleman, it can't be on either end of the pipeline. So that brings me to my next question - how did you get it to work? As in local repo to git repo to service sync?

[KevinChant]

Hi, I very quickly tested created a paginated report and it looks like it needs to be in a specific schema format. So I suspect your suspicions are right about having to create in the service, at least for now. Until there is a way to save it locally with the below schema definition (or attempt to create the schema definition locally first).

I hope this helps.

[pborah]

Yepp that seems to be it. Unfortunately report builder doesn't save paginated reports in that format directly so yes for now service will have to be a middleman to facilitate that. This is what our devops expert said the other day as well as a possible reason/clue.