Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi
New to Fabric and trying basic integration with Git.
I have commited a Warehouse to Git (Azure Devops) it contains 1 schema and table so very basic. If I create a new workspace and connect to that repo, it looks like it starts to sync down, then I get an error. Not sure how to troubleshoot this. It seems like a bug to me but not sure. Cant seem to find any known issues about this either. Anyone have any ideas?
Solved! Go to Solution.
Hi @schneiw ,
Thanks for posting in Microsoft Fabric Community,
There is an active known issue in Microsoft Fabric related to Git integration with Warehouses.
Known Issue Description:
"When working with a second workspace in Fabric, whether by creating it manually or using the "Branch out to another workspace" feature, customers will not be able to update the warehouse from Git."
Symptoms:
"Warehouse artifact will have "Uncommitted" git status after connecting to git in 2nd workspace, Git source control panel will have + and - shown in Changes tab, in network/browser trace, the logical id returned for the warehouse will have 0000 guid."
At this time, there is no published workaround. It’s recommended to continue managing the Warehouse from the original workspace where it was committed.
We understand this may be frustrating, and we apologize for the inconvenience. The product team is aware and actively working to improve Git support for Warehouse artifacts.
Thanks for your patience while this is being resolved.
Hope this helps. Please reach out for further assistance.
Please consider marking the helpful reply as Accepted Solution to assist others with similar issues.
Thank you.
Hi @schneiw ,
Thanks for posting in Microsoft Fabric Community,
There is an active known issue in Microsoft Fabric related to Git integration with Warehouses.
Known Issue Description:
"When working with a second workspace in Fabric, whether by creating it manually or using the "Branch out to another workspace" feature, customers will not be able to update the warehouse from Git."
Symptoms:
"Warehouse artifact will have "Uncommitted" git status after connecting to git in 2nd workspace, Git source control panel will have + and - shown in Changes tab, in network/browser trace, the logical id returned for the warehouse will have 0000 guid."
At this time, there is no published workaround. It’s recommended to continue managing the Warehouse from the original workspace where it was committed.
We understand this may be frustrating, and we apologize for the inconvenience. The product team is aware and actively working to improve Git support for Warehouse artifacts.
Thanks for your patience while this is being resolved.
Hope this helps. Please reach out for further assistance.
Please consider marking the helpful reply as Accepted Solution to assist others with similar issues.
Thank you.
Hi Team,
We did not notice the issue occurring when branching out to a new workspace, and was asking you to confirm if this issue was specifically resolved between the two versions which I listed below:
Data Location : Australia Southeast (Victoria)
Service version 13.0.25729.43 -- Issue occuring
Service version 13.0.25778.49 -- Issue not occuring
Ask:
In the patch notes between these two service versions, was this issue identified as being targeted for resolution or is this potentially something that could reoccur?
Hi @roshinikumarkar ,
Thanks for sharing the details and comparing the behavior between the two service versions.
This issue is still listed as an active known issue here:
Known Issue 1103 – Data Warehouse Git Sync Fails in Second Workspace
There’s no information yet in the documentation about a fix, service versions, or region rollout. So we can’t confirm if this issue was fixed between versions 13.0.25729.43 and 13.0.25778.49 or if it might happen again.
We’ll keep an eye on the known issues list and share any updates if Microsoft adds more details.
Appreciate your testing and input on this.
Thank you for your response. Any workaround, please suggest or else please keep posted for any further updates on this fix
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Fabric update to learn about new features.
User | Count |
---|---|
4 | |
4 | |
2 | |
2 | |
2 |