Hello Fabric Product Team,
I would like to highlight a key limitation in the current Microsoft Fabric Notebooks experience regarding code modularity and reusability.
Currently, the “builtin” resources folder is scoped to each notebook, meaning that Python modules placed in one notebook’s “builtin” directory are not accessible to other notebooks in the workspace. As a result, any reusable Python code (utility functions, connectors, etc.) must be manually copied into the “builtin” folder of every notebook that needs it. This approach goes against best practices like DRY (Don’t Repeat Yourself) and creates significant maintenance, versioning, and collaboration issues for data engineering teams, especially on large-scale projects.
Request:
Please consider introducing a “shared” Python resources folder or a workspace-level global modules directory, allowing all notebooks in a workspace to import and reuse common Python scripts (.py files) without duplication.
This enhancement would dramatically improve code maintainability, encourage reuse, and align Fabric with other leading data platforms that support shared library mechanisms.
Thank you for your attention.
Best regards,
Marc P.
miguel
on:
Personalized Source List in Get Data
on:
RLS testing UI (Test RLS roles directly in the ser...
on:
DO NOT CONVERT my Workspace to Fabric Free Trial W...
on:
MS Fabric: Manage Connections and gateways with Fo...
on:
CU% over time: Filter by workspace (Capacity Metri...
YSD
on:
Support the SSE protocol as Fabric Eventstream sou...