Hello!
It seems like Microsoft has introduced yet another bug with some recent updates to the warehouse object in Fabric. I truly don't understand how you can have a SaaS product that releases new features but breaks old fixes / brings in new issues. I totally understand that this is a new product and that some objects are still in preview, but it's frustrating to always keep this in mind when developing within this product. We can't keep breaking existing stuff just because we introduce new stuff that hasn't been tested enough with the newly introduced features.
My team and the project I have managed for about 6-7 months has an architecture that's git-integrated in all areas. Whether we're developing something new or pushing a feature/hotfix etc., we use git for everything. During these months, issues have arisen within the Fabric UI when connected to a repository (DevOps repo in our case), but we have found workarounds and fixed most problems. The recent issue, though, is something we really can't work around.
To understand the problem in-depth, you have to understand our workspace structure when it comes to developing. We have a Production workspace + several developer workspaces like DEV - W1 etc. which are static workspaces that a developer connects to with their corresponding branch (new or old). Until now, we have had around 4 developer workspaces that we share within our team, so whenever someone is done with their developing in a workspace, they disconnect their branch so it frees up for someone else to use. This has worked for us and has helped us keep everything we do within Fabric source controlled.
But now to the actual problem that has been re-introduced and is not intended behavior in my opinion.
This week (2025-04-23) I needed to create new developer workspaces since our team is growing. But when I finish some small pre-configuring within the new workspace and finally am going to connect a testing branch to see that everything works as intended within this new workspace, the sync happens and everything looks good until the sync is finished. We get an issue on all warehouse objects in the repo; Fabric tries to delete our existing warehouse object as it is in our repo and recreate it. But it tries to recreate the objects with new logicalId compared to the ones we already have declared. This can easily be observed when looking into DevOps after we try to commit the changes to get a better understanding of what's happening (specifically .platform file for the objects).
I am guessing that this issue arises because the warehouses in our repo was not created within this new workspace, they were created in another workspace and therefore it does not recognice the logicalId and tries to deleted the object we have and create a new one with a logicalId it regonices. This has not been a issue going back some months/weeks and has been introduced recently.
Another comic thing connected to the first lines of text I wrote, is that if you have a old workspace that is created before this "update" for workspaces that introduces this issue, everything works as before. So our existing developer workspaces works as intended and does not force me to change the logicalIds when I connecting a new branch from the same repo to it. In my opinion that means that this is a bug, since if this was something that was introduced and is as intended? It should be affecting both my old and new workspaces, not only the new ones. We need a fix for this asap.
Commit log when I connect our repo to the new developer workspace:
Reddit post that talks about a similar issue (could be the same and that is has been re-introduced).
Helpful resources
Join our Fabric User Panel
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Fabric Monthly Update - June 2025
Check out the June 2025 Fabric update to learn about new features.
Fabric Community Update - June 2025
Find out what's new and trending in the Fabric community.
