Allow recovery of artifacts that have been deleted from a workspace; dataflows, pipelines, notebooks, etc.. Have a recycle bin per workspace for quick navigation & recovery.
5 Comments
- nishalitNew Member
When an item gets deleted (Lakehouse, Warehouse, Notebook, Report, Pipeline, etc.) it should go to a recycle bin first.
It should stay there for some days before it gets completely deleted. I suggest 14 days as a good time period. Or it can be adjustable time period.
This way, if someone accidentally deletes an item, it will be possible to recover the item and it's data.
It should also be possible to delete an item from the recycle bin to completely delete the item, in order to avoid unnecessary storage costs.
There should be a recycle bin for each workspace. The workspace members can recover items from the recycle bin.
If a workspace gets deleted, it should be possible for the Fabric Admin or Capacity Admin to recover the workspace.
- sakshi399
Microsoft Employee
We are evaluating this idea and its timeline along with other priorities. Your comments and votes will help us plan and design the feature. Thank you for your feedback! - fbcideas_migusrNew MemberStatus added:Under Review
- SJCuthbertson
Advocate I
A related point (I'm not sure it's worth a separate Idea?) that I saw in r/MicrosoftFabric today, was that the act of deleting items should work like deleting a repo in Azure DevOps or GitHub. Specifically, it's a two step process. You have to click a delete button that is clearly marked as "this is dangerous!" and separated from other things in the UI. THEN you have to type in the name of the thing you want to delete, before you can click to confirm. Deleting things in Fabric UI should be this hard. Perhaps not everything: if git is enabled for the workspace, then deleting code-only objects like pipelines and notebooks could be streamlined. But deleting items in a non-git workspace, and deleting lakehouses/warehouses/eventhouses anywhere, needs this added protection. - yicw
Microsoft Employee
Status changed:Under ReviewtoPlanned
Recent ideas
Sparklines: customizable data point limit (allow more than 52 points)
Sparklines in table and matrix visuals currently display up to 52 data points per sparkline. We'd like to suggest a customizable data point limit, so report authors can allow more than 52 points and ...v-kkalvala4 hours agoMicrosoft EmployeeNew14Views2likes0CommentsAllow dynamic headers for Calculation Groups
calculation Groups reduce duplicated DAX, but their Calculation Item names become static Matrix headers such as Current, MTD, QTD, and YTD. These headers do not tell report consumers which measure i...danieleloFabric7 hours agoNew MemberNew9Views1like0CommentsCentralized retention policies for imported data in Power BI semantic models
Summary Please provide a tenant-level retention policy that allows administrators to centrally enforce automatic deletion of expired data from Power BI Import semantic models, independently of data ...JINHOYOO7 hours agoMicrosoft EmployeeNew64Views19likes1CommentResizable Personalize visual pane or wrapped field names
Problem: The Personalize Visual pane width is fixed and long measure/column names are cropped making it difficult for users to identify which item to add to their visual. Idea: Allo...Simon_AUS13 hours agoRegular VisitorNew45Views8likes0Comments