Forum Discussion
Update errors when trying to connect new workspace to new Git branch created from main
Hi, I'm trying to set up multiple Fabric workspaces connected to different Git branches so that my team can collaborate. The branches are created from main and connected to empty workspaces, but I get errors during sync. The errors vary but I mostly get errors related to the DataflowsStagingWarehouse. See images below. Has anyone else had the same issue?
Thanks in advance!
6 Replies
v-cboorla-msftMicrosoft Employee
Hi kkfk68
Thanks for using Microsoft Fabric Community.
Apologies for the inconvenience that you are facing.
The error you are encountering in Microsoft Fabric "dataflowsstagingwarehouse" while setting up multiple Fabric workspaces connected to different Git branches suggests a conflict.
Please refer to the link this might help you : Working with Microsoft Fabric Git integration and multiple workspaces
For similar issue please refer this thread : Solved: Best practice for Git integration for multiple wor... - Microsoft Fabric Community
If the issue still persists, please do let us know. Glad to help.
Thank you.
Hi and thank you for your response.
I agree that there seems to be a conflict, but I don't understand how there could be a conflict when the workspace was empty? I am also struggling to find a way to resolve the conflict so that I can use the new workspace for development. Please advise if you have any suggestions.
Thanks in advance!
- v-cboorla-msft
Hi kkfk68
Yes, an empty workspace shouldn't inherently cause conflicts during the initial sync with a Git branch. Here are couple of reasons that might help you, why you are still encountering errors related to DataflowsStagingWarehouse.
- Even though the workspace appears empty from your perspective, there might be hidden files or configurations related to DataflowsStagingWarehouse inherited from the main branch. These might be causing conflicts during the sync.
- It's possible the new branch you created from main wasn't entirely "empty" from a Git perspective. There might be hidden Git commits or configuration files related to DataflowsStagingWarehouse that are being pulled during the sync and causing conflicts.
- Try completely deleting and recreating the workspace before connecting it to the new Git branch. Ensure you have a backup of any configurations you might need to restore later.
Sometimes, cached data in Fabric can lead to unexpected behavior.
Temporary Glitch: Clearing cookies and caches can sometimes resolve temporary glitches within the application that might be causing the issue.
Corrupted Data: In rare cases, corrupted data stored in the browser's cache related to Microsoft Fabric might be causing the issue. Clearing the cache removes this potentially problematic data.
Hard Refresh: A hard refresh bypasses the cached version of the webpage and forces the browser to download the latest version from the server. Press Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac).
Try Microsoft Edge: If you are currently using Chrome or Firefox, try switching to Microsoft Edge to see if the issue persists. Edge is the native browser for Microsoft products and might have better compatibility with Microsoft Fabric.
If the issue still persist, please do let us know. Glad to help.
I hope this information helps.
Thank you.
- v-cboorla-msft
Hi kkfk68
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond back with the more details and we will try to help.
Thank you.
re84ukHelper I
Hi
I am suffering from the same problem. Do we know what the resolution to this is?
