Forum Discussion
bug? Mass changes in workspace
Hi there!
This morning i was faced with a ungodly amount of changes in my workspace. Nearly all semantic models and dashboarding were stated to have a conflict according to source control. After which we obviously went into panic mode and reverted everything, especially because nothing was shown in our repo the workspace is connected to.
After investigating, we found that just about every update was regarding a version for the used scheme.
Can someone please explain to me if this is expected behaviour, and if it is, explain how we can check if its a mass version update BEFORE committing or undoing?
decarsul right. Even you can try to solve this issue by flowing the guideline by @ SolomonovAnton
in here : https://community.fabric.microsoft.com/t5/Service/Suddenly-all-of-our-semantic-model-shows-conflict-in-workspace/m-p/4768714#M281537
5 Replies
decarsul Seems like due to having some internal sync issue or service update, you are having schema version change issues. It's better to create a support ticket with Microsoft and get help.
To create a support ticket, visit https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket.
Here is another helpful post, its mentioned,fabric introduced folder support in Git and you are getting conflict for this. Check this out https://community.fabric.microsoft.com/t5/Service/Suddenly-all-of-our-semantic-model-shows-conflict-in-workspace/m-p/4768714#M281537
Find this helpful? ✔ Give a Kudo • Mark as Solution – help others too!So you can confirm, this is not expected behaviour. That is what i needed to know before creating a support ticket. Thank you.
decarsul right. Even you can try to solve this issue by flowing the guideline by @ SolomonovAnton
in here : https://community.fabric.microsoft.com/t5/Service/Suddenly-all-of-our-semantic-model-shows-conflict-in-workspace/m-p/4768714#M281537
Hi decarsul ,
Thank you for bringing this issue to our attention.Based on your description, multiple conflicts suddenly appearing in your semantic models and dashboards, without any changes reflected in your connected Git repository, this does not appear to be expected behavior.
Microsoft Fabric recently introduced folder support in Git, as indicated in your Source Control banner. This update may have led to internal schema changes, which could explain the unexpected conflicts.
Since you have verified that there were no manual changes and your Git repository is up to date, I recommend submitting a support ticket with Microsoft, as advised in the community.
To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
Thank you.
Hi decarsul ,
To clarify, this is most likely due to the new Git folder support. Check the Updates tab and preview a few files - if you see changes only in folder paths or schema versions, you can confidently commit. Only consider reverting if there are actual model logic changes.
This guidance should help you resolve the issue. If you have further questions or need assistance, feel free to reach out we’re ready to support you.
