Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
When deleting this notebook, I am just getting this error message:
Can't delete the Notebook 'DELETEME'. Other items are dependent on this one and may be affected. To see which items are affected items, go to Lineage view.
This stops me from merging out from a new branch in git. completely blocked.
Solved! Go to Solution.
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:
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:
Is there any way for admin to know the dependency across branches of all members?
Hi @ex_kjetilh ,
This usually happens when the notebook you’re trying to delete is being referenced somewhere else for example, inside a pipeline activity, a dataflow, or another notebook. Fabric blocks the deletion to avoid breaking those dependencies.
To resolve it:
Open the Lineage view for the notebook.
Check which items (pipelines, dataflows, etc.) are connected to it.
Remove or update those dependencies first.
Once nothing depends on it, try deleting the notebook again — it should work.
If you’re using Git integration, make sure all linked items are committed or removed from the current branch before merging.
After that, refresh the workspace and retry the delete operation.
Best regards,
Gopi Krishna
Hey @ex_kjetilh,
That error usually means there are still dependencies linked to that notebook — maybe some reports, dashboards, or jobs referencing it. Try opening the Lineage view like the message suggests, and check if any downstream items depend on it. Once you unlink or delete those, you should be able to remove the notebook.
It’s kind of like real life — when you’re stuck and can’t move forward until a few things get cleared up first. Having the right support system makes a huge difference, just like how bail bonds tampa helps people get unstuck when things are holding them back. Hope this helps you get your branch merged cleanly!
I deleted all the pipelines. As shown, there is no lineage.
Hi @ex_kjetilh,
Are there pipelines that run this notebook? If so the pipelines need to be edited so they no longer have the notebook activity in them before you can delete the notebook.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.