Forum Discussion
HELP cannot delete notebook
SOLVED:
In lineage view there is a little button on each of the boxes with the hover over help text: "show impact across workspaces". The problem was that even if was 1 dependency, we could not see which workspace or which resource in that workspace, so we thought it must be a bug.
However, it turned out a person had created a "branch out to new workspace" that nobody else knew about and created a pipeline in it that referred to the notebook. (And no, it was not synced to git either) And because default access to branched out workspaces is only the person branching out - nobody can see what is going on. So, creating a branch and experimenting in that branch is not quite without risk.Lesson learned: When using branching in Fabric:
- Share branch workspaces with the team (via Manage Access to add all other team members as contributor users).
- Check dependencies across workspaces on an item before merging a delete on an item.
SOLVED:
In lineage view there is a little button on each of the boxes with the hover over help text: "show impact across workspaces". The problem was that even if was 1 dependency, we could not see which workspace or which resource in that workspace, so we thought it must be a bug.
However, it turned out a person had created a "branch out to new workspace" that nobody else knew about and created a pipeline in it that referred to the notebook. (And no, it was not synced to git either) And because default access to branched out workspaces is only the person branching out - nobody can see what is going on. So, creating a branch and experimenting in that branch is not quite without risk.
Lesson learned: When using branching in Fabric:
- Share branch workspaces with the team (via Manage Access to add all other team members as contributor users).
- Check dependencies across workspaces on an item before merging a delete on an item.
Is there any way for admin to know the dependency across branches of all members?