Forum Discussion
dynamic library variables
Hi krhacke
As of now, Microsoft has not officially announced that this feature will be included in the General Availability (GA) release either. Library variables must be referenced statically in the pipeline at design time, and expressions like @concat()or indexing into pipeline().library variables dynamically are not evaluated in a way that resolves the actual variable content.
If supporting dynamic referencing of library variables is important for your use case, it’s recommended to submit feedback via Microsoft Fabric Ideas so that it can be considered for future updates.
Thank You!
Hi v-karpurapud - thank you for your response!
You mentioned that dynamic construction of library variables isn't supported in the current preview. Is this something that will be included in the GA release?
We currently hardcode workspace and notebook guids in each of our source systems' notebook json workbenches. However, as these change from dev to test to prod workspaces, my client feels it's burdonsome to have to update these at each step in each workbench. It would be great to be able to set these name / guid values in a library variable once, then use just the name for each in the json.
Hi krhacke
As of now, Microsoft has not officially announced that this feature will be included in the General Availability (GA) release either. Library variables must be referenced statically in the pipeline at design time, and expressions like @concat()or indexing into pipeline().library variables dynamically are not evaluated in a way that resolves the actual variable content.
If supporting dynamic referencing of library variables is important for your use case, it’s recommended to submit feedback via Microsoft Fabric Ideas so that it can be considered for future updates.
Thank You!