Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
Anonymous
Not applicable

Developer mode & git for reports with live connection

Hello!

I currently have two reports that share the same dataset published, hence are connected to that dataset via live connection

 

I want to start using version control for this reports and that includes for example any metrics created at the dataset level but i'm not sure what are the best practices right now.

 

In the future I want to have everything being automated via deployment pipelines as well

 

So my questions is, has anyone tried the developer mode with live connection and if yes what best practices or setup do you recommend?

 

 

12 REPLIES 12
D_Lav
Helper I
Helper I

Hi @RuiRomanoMS 

 

Maby im missing somethhing but i dont understand how this could be by design. If the architecture suggests to separate workspaces for semantic models and reports. You could never use GIT integration for the report part as it is now? 

 

Is there a workaround for this or should we live with the fact that reports connected to a semantic model in a separate workspace can´t be git connected? 

When reports and semantic models live in different workspace there is no problem, the byConnection will be preserved when exporting to Git.
Only when both report and semantic live in the same workspace, when exporting to git because they are in the same workspace the definiton.pbir of the report will be by default as a relative byPath connection.

Thanks @RuiRomanoMS for the reply.

 

Maby its a separate error then.. I have created a simple report connected to a semantic model in development stage and then, save it as a PBIP, push it to development branch in origin and try to sync the branch in my report workspace i get the following error. 

D_Lav_0-1713419348675.png

 

I have used the connect to PBI Semantic model connector. 

its only a small table in the report. 

The definition file does indeed validate what you said so i guess that looks good?

D_Lav_1-1713419703187.png

 



Are you connecting to a semantic model in "My Workspace"? Or to Azure/SQL Analysis Services?

Hi @D_Lav 

I didn't check the definition file in such detail.

But I got a different effect.

 

The synced report works without any issues.

But I cannot edit it in Power BI Desktop after syncing it back from Git.

 

Perhaps it's the same cause.

I don't know.

Hi @SalCag 

 

I tried that now aswell. If i publish the report to the workspace with a connection to a semantic model in separate workspace. I can sync the content to git from workspace but not the other way around. 

 

And the reports dont work in pbi desktop after. So same effect as you. 

 

This seem to wonky to work with in real life..

But it's still a problem that it's impossible to properly work with reports with a Live connection while integrating them in Git.

 

To be honest, I don't care about why.

The fact is that it's a pain.

Maybe worth adding an override option that always uses absolute addressing.

SalCag
Regular Visitor

Hello

 

This is neither intuitive nor easy to work with.

I expect to keep it as a life connection.

This way, I must manually publish reports with a live connection, which defies all the benefits of Developer mode.

 

It's not possible to sync a report to the workspace from Git with a live connection. When I need to change it and sync it back to Git, it is changed, and I cannot continue to work without hacking the files.

 

Regards

Salvatore

The reports are always published as live connection, the only difference is on local development. 

When both report and model live in the same workspace, by default, Fabric Git Integration will export with a relative connection letting you when opening in Desktop author both model and report. If you dont wish to refresh the model locally, you can temporarily switch to live connection.

But on publish using Fabric Git, even if its a byPAth the report will always be published connected to the model. Same as if you publish with Live Connection.

SalCag
Regular Visitor

Hello

 

I started working with it during the last few days.

But I encountered a very odd behavior:

  1. I create a report and connect it to a Power BI semantic model
  2. I save it as a project
  3. Commit to my Git Repo
  4. Update the workspace connected with my Git Repo

Immediately after the workspace update, Power BI told me that something had been updated.

In fact, Git integration tells me that the report uploaded to the workspace from Git has been changed.

 

I commit the change to Git.

Then, I pull the new version to my local folder and open the report.

 

Now, all tables are converted to Import mode.

The information on the status line at the bottom of the Power BI desktop window has disappeared.

When I open Power Query, I see the M-Code for all tables, which should not be possible with a live connection.

 

The only way to circumvent this is to manually publish my reports to the workspace instead of relying on Git.

 

I hope that this will be changed in the Git integration on the Power BI service.

 

Regards

Salvatore

 

Thanks for the feedback. This behavior is by design, when report and semantic model share the same workspace they get exported to Git with a relative connection: byPath. Learn more here: https://learn.microsoft.com/en-us/power-bi/developer/projects/projects-report#definitionpbir

If you still wish to open the report in live connect, you can temporarily replace the definition.pbir with a by a byConnection connection. But after publishing to service, it will be swapped by a byPath. 

 

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.