Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
In ADF and Synapse you can get the Workspace name from the System Variables in the Expression Builder as seen below. But in Fabric Data Factory pipelines you only get the workspace ID which is a GUID.
I really need to be able to grab the workspace name as that is used to dynamically set a variable as the workspace name contains the env in the name (DEV/UAT/PRD). The workspace name is also helpful for us to dynamically pull from those different storage accounts and an email is sent when the pipeline fails detailing which workspace was run etc...
Synapse Pipelines:
ADF Pipelines:
Microsoft Fabric:
Solved! Go to Solution.
Hi @12angrymentiger ,
Thanks for using Fabric Community.
Currently this option is not available but we are open for feedback to improve our product.
Appreciate if you could share the feedback on our feedback channel. Which would be open for the user community to upvote & comment on. This allows our product teams to effectively prioritize your request against our existing feature backlog and gives insight into the potential impact of implementing the suggested feature.
Hope this helps. Please let me know if you have any further queries.
Really need this now that data pipelines are git-supported.
Being able to reference a resource (ex. lakehouse inside of a notebook) that belongs to the same workspace that the data pipeline is associated with is essential for limiting execution scope. Before pipelines became supported, you could hard code the workspace name as a pipeline parameter since the pipelines weren't associated with each other.
Hi @12angrymentiger ,
Thanks for using Fabric Community.
Currently this option is not available but we are open for feedback to improve our product.
Appreciate if you could share the feedback on our feedback channel. Which would be open for the user community to upvote & comment on. This allows our product teams to effectively prioritize your request against our existing feature backlog and gives insight into the potential impact of implementing the suggested feature.
Hope this helps. Please let me know if you have any further queries.