Forum Discussion
Memorable MemberPower BI Git Integration - Everything is Gone
Hi dbeavon3 ,
Thanks for posting in Microsoft Fabric Community,
I completely understand your frustration. Git in Fabric is designed for managing source code, not large datasets, which is why it can sometimes lead to unintended deletion of untracked resources like datasets. Git integration should ideally not affect datasets or important data by default.To help prevent something like this in the future, here are a couple of suggestions:
- Store Datasets Separately: To avoid losing critical data, try storing datasets and other key resources outside of Git-controlled elements, like in Lakehouses or other dedicated storage solutions.
- Use Backup Strategies: Regularly back up your workspace resources, especially datasets, to ensure nothing important gets lost during syncs with Git.
Just wanted to check in—were you able to restore your workspace through Mindtree?
Since the "hot" recycle bin retention is 7 days, I hope you were able to recover everything. Let me know if you need any further assistance!Best regards,
Vinay.Hi dbeavon3
It seems that while using Git integration in Power BI, you committed some assets (like notebooks and pipelines) to a Git repo and forgot to detach it afterward. This caused Power BI to sync your workspace with the Git repo, likely removing datasets, dataflows, and other assets not tracked in Git. Git doesn’t handle data storage, so it might have overwritten or deleted datasets in the process.
Since this wasn’t in a production workspace, you should contact Mindtree or Microsoft Support to see if they can restore your lost data. Going forward, always ensure Git is detached after use and back up datasets separately to avoid this issue.
Did I answer your question? Mark my post as a solution, this will help others!
If my response(s) assisted you in any way, don't forget to drop me a "Kudos" 🙂Kind Regards,
Poojara
Data Analyst | MSBI Developer | Power BI Consultant
Consider Subscribing my YouTube for Beginners/Advance Concepts: https://youtube.com/@biconcepts?si=04iw9SYI2HN80HKS
Community SupportHi dbeavon3 ,
Thanks for posting in Microsoft Fabric Community,
I completely understand your frustration. Git in Fabric is designed for managing source code, not large datasets, which is why it can sometimes lead to unintended deletion of untracked resources like datasets. Git integration should ideally not affect datasets or important data by default.
To help prevent something like this in the future, here are a couple of suggestions:
- Store Datasets Separately: To avoid losing critical data, try storing datasets and other key resources outside of Git-controlled elements, like in Lakehouses or other dedicated storage solutions.
- Use Backup Strategies: Regularly back up your workspace resources, especially datasets, to ensure nothing important gets lost during syncs with Git.
Just wanted to check in—were you able to restore your workspace through Mindtree?
Since the "hot" recycle bin retention is 7 days, I hope you were able to recover everything. Let me know if you need any further assistance!
Best regards,
Vinay.
dbeavon3I appreciate your post, and your sincere concern. The reason for the public post is because I'm not that embarrassed to share my mistake, and I want others to be aware of the potential risks in attaching a workspace to a git repo. I'm guessing lots of people have made similar mistakes, but I wasn't actually finding any of the horror stories when I googled for it.
... Again, it was an experience that was unlike every other experience I've had with git. Normally the use of git should give people a warm-and-fuzzy sense of confidence and reassurance that their assets will not be lost.... But in Power BI, it is the exact opposite! In the future, I will always be nervous to introduce git to a workspace; and I'm guessing I'll probably never be brave enough to hook it up to a production workspace.
>> unintended deletion of untracked resources like datasets. Git integration should ideally not affect datasets or important data by default.
Right. There should at least be a configuration option (checkbox) that determines whether a user wants their datasets to be managed under the same umbrella as their python notebooks.
>> "Store Datasets Separately"
I immediately came to the same conclusion you did. Perhaps I had missed some "best practice" whereby users are warned away from from enabling git on any workspace that contains data or datasets? I'm guessing that these PBI workspaces will eventually need to "specialize", and serve in the capacity of EITHER hosting data, OR hosting programming assets (... but NEVER serving in both capacities.) Otherwise the risks of the git integration are too high and Fabric is liable to blow away our stuff.
I don't know if Microsoft is listening, but I think there is an INCORRECT assumption that all the users of Power BI know how to open a support ticket and know how to ask for an engineer to clean up the messes that happen. This incorrect assumption seems to allow Microsoft to create solutions that take unnecessary risks on behalf of their users. For each PBI user (like myself) who is very familiar with the SOP of calling Mindtree to clean up a PBI mess, there are probably two or three users who are NOT familiar with it. Those people are fending for themselves, and are probably not recovering any of their data in a similar scenario. I think there is a "moral hazard" that is present, given that the Microsoft PG assumes that Mindtree will step in and clean up all the messes that arise from the incorrect use of this git integration.
- ecalzavara
Advocate II
Hey mate, thanks for your post.
Did you manage to recover the deleted files, eventually? It happened the same to me, contacted the MS Support and they said there is no way to recover deleted artifacts from a workspace when deleted via git.... which sounds weird to me, but it could be the case. Just checking if you eventually managed somehow to recover the lost data. I was so surprised a company like MS doesn't have a disaster recovery option for this sort of actions they deployed on publicly available products.
Thanks.
