Skip to main content
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Next up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now

lysdexia

Power BI Source Control Does not Allow One to Check out the main Branch

Submitted by on ‎06-09-2023 10:03 AM

I recently added source control to a Power BI workspace.

 

I was able create a new branch (which is called "Checkout new branch"), make changes to a report, and commit the changes.
I was able to see the changes in the branch in Azure DevOps, and merge them into the main branch. The merge removed the working branch during the merge. I am not able to check out the main branch.

 

nice-one.png

 

Power BI / Fabric:

  1. does not seem to be aware of the merge
  2. does not give one the option to switch back to the main branch
  3. will only let me create a new branch

The most basic flow I can think of is new branch from main --> do work --> test --> merge branch to main --> relax with my thoughts. Is this possible with Source Control in Power BI? I can't imagine this is the expected behavior.

 

Status: Needs Info
See more ideas labeled with:
12 Comments (12 New)
Comments
lysdexia
Regular Visitor
‎01-10-2024 06:10 AM

So, it appears that the "missing" workspace branch settings are happily living under `Workspace Settings` -> `Git integration` -> `Branch`. I have no clue whether this was always the case, or I and others like me just didn't drill down deep enough.

 

Why the option to create a new branch, which is then, to all appearances, locked in as the default working branch for the workspace appears in the top-level `Source control` menu is bizarre. Wouldn't it make more sense to have both options in the same place, and have access limited by role? It might even be nice to have a link to the project on dev.azure.com or github in close proximity, thereby passively spreading knowledge of how devs tend to interact with version control, thereby empowering the user (and keeping us from asking stupid questions, which to all appearnces you'll ignore anyway?)

 

Thanks to @lorcan17 for showing us (okay, probably just me) the buried branch change option. Good on you!

rc449
New Member
‎02-07-2024 12:55 AM

Hello Team,

 

I am facing this same issue with switching between branches.

I think an admin may be able to switch between branches by going to workspace settings => Git Integration.

I think any uses who have access to edit reports should have access to switch between branches.

 

I hope microsoft will fix this issue.

Thanks,

Idea Statuses