Is it possible to use the relative path of tables within a lakehouse instead of the absolute path?

[0_0]

I'm trying to update a notebook to utilize the relative path instead of the absolute path to update the lakehouses within the development workspace however I want to push to the production workspace, and do the same to the lakehouses relative to the workspace. I'm open to other suggestions.

Thanks!

[v-lgarikapat]

Hi @0_0 ,Thanks for reaching out to the Microsoft fabric community forum.

@nilendraFabric , @burakkaragoz 

Thanks for your prompt response

In addition to @nilendraFabric  and @burakkaragoz , I'm including the learning document it may help you as well, 

Load data into your lakehouse with a notebook - Microsoft Fabric | Microsoft Learn

We appreciate your engagement and thank you for being an active part of the community.

Best regards,
LakshmiNarayana.

[v-lgarikapat]

Hi @0_0 ,

I wanted to check if you had the opportunity to review the information provided  , Please feel free to contact us if you have any further questions. If my response has addressed your query, please "Accept as Solution" so other members can easily find it.

Looking forward to your response.

Best Regards,

Lakshmi Narayana

[v-lgarikapat]

Hi @0_0 ,

If your issue has been resolved, please consider marking the most helpful reply as the accepted solution. This helps other community members who may encounter the same issue to find answers more efficiently.

If you're still facing challenges, feel free to let us know we’ll be glad to assist you further.

Looking forward to your response.

Best regards,
LakshmiNarayana.

[v-lgarikapat]

Hi @0_0 ,

As we haven't heard back from you, we are closing this thread. If you are still experiencing the issue, please feel free to create a new thread we’ll be happy to assist you further.

Thank you for your patience and support.

If you found our response helpful, please mark it as Accepted Solution so others with similar queries can find it easily.

Best Regards,

Lakshmi Narayana

[nilendraFabric · Accepted solution]

Hi @0_0 

Relative paths work only when the lakehouse is mounted to the notebook. The mounted lakehouse is visible in the Lakehouse explorer, and you can use `/lakehouse/default/...` for your tables and files

If you share or deploy the notebook to another workspace, the mount point may not be the same, and the relative path may not resolve correctly unless the lakehouse is mounted in the same way

When using deployment pipelines to move content from development to production, the lakehouse references in notebooks and Spark job definitions can be remapped to reference a different lakehouse in the target workspace if configured accordingly

I would recommend to Use variables or parameters to specify the lakehouse path in your notebooks, making it easier to update when moving between workspaces or environments.

[burakkaragoz]

Hey @nilendraFabric ,
Your answer explained everything really well, thanks for breaking it down. Using variables or parameters for the lakehouse path is a super useful trick that I’ll definitely try out. Appreciate the clear tips!