Forum Discussion
Git and ADO Integration with Live Connection
Hi Anonymous ,
When you try to sync between a git repository and a workspace, it seems that you're getting an error.
Here are some suggestions for you:
1.Make sure your Git and Azure DevOps integrations are set up correctly, as your connection will report an error if misconfigured
2.As for the error message you see, it might be related to the fact that the PBIP file does not contain a data model. The "DiscoverDependencies" function may be trying to find a data model in the PBIP file, but it fails because it doesn't exist.
3.You can try switching to a PBIX file to connect to the data source in real time
Below is the Microsoft's link:
Use Azure CLI to share Git code - Azure Repos | Microsoft Learn
Git integration with Power BI Desktop projects - Power BI | Microsoft Learn
Best Regards,
Xianda Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- Anonymous2 years agoNot applicable
I don't believe it's related to the setup being misconfigured, but rather something to do with how PBI files created with live connections do not contain a dataset definition. It seems to only contain the report definition. But I don't see any official MS documentation explicitly explaining this and how this impacts git integration when using PBIP files.
Ideally, we would want our developers to push their PBIP changes from their local to remote repos, and then have the repo sync with the PBI workspace. But does having a live connection prevent all of this from being possible?
- lbendlin2 years ago
Super User
If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .- Anonymous2 years agoNot applicable
Thanks for the suggestion! Forgot about support tickets.
I ended up finding the documentation on supported items for git integration. Turns out live connections aren't yet supported. So I guess the workaround is to publish as PBIX instead?