Forum Discussion
Read Notebook cell string from another notebook
Fabric does not expose notebook cell contents through the public APIs today. Get Notebook Definition only returns metadata, not the code or markdown cells which is why the body field is always null. I believe the product team has not exposed any API to fetch notebook source programmatically.
Possible options as of today:
Store your SQL logic in external files (Lakehouse, Git, or a mirrored repo) and have notebooks read from there. Then you can parse those files easily.
Use Fabric Git integration (if enabled) and parse the notebook source from the .ipynb representation in Git. That is currently the only reliable method to get notebook content automatically.
Move your transformation logic into pipelines, dataflow gen2 or SQL scripts if you want first class lineage parsing.
But directly reading notebook cell strings from another notebook or API is not supported today.
Fabric does not expose notebook cell contents through the public APIs today. Get Notebook Definition only returns metadata, not the code or markdown cells which is why the body field is always null. I believe the product team has not exposed any API to fetch notebook source programmatically.
Possible options as of today:
Store your SQL logic in external files (Lakehouse, Git, or a mirrored repo) and have notebooks read from there. Then you can parse those files easily.
Use Fabric Git integration (if enabled) and parse the notebook source from the .ipynb representation in Git. That is currently the only reliable method to get notebook content automatically.
Move your transformation logic into pipelines, dataflow gen2 or SQL scripts if you want first class lineage parsing.
But directly reading notebook cell strings from another notebook or API is not supported today.
I can confirm linking the workspace to devops, then using the devops API to find notebook-content.py files under whatever location you have files saved in, you can grab the file.text directly. 👍
