Forum Discussion
Variable Library binding to OneLake SharePoint Shortcut Target Subpath is not persisted
Hi,
I'm trying to use a Fabric Variable Library to manage SharePoint Shortcut paths across DEV, QA and PRD.
I use the same SharePoint connection in all environments, but different document libraries:
- DEV: Shared Documents
- QA: Quality
- PRD: Production
For example, I created a variable for the dimensoes shortcut with:
- DEV: /sites/Analytics/Shared Documents/dimensoes
- QA: /sites/Analytics/Quality/dimensoes
- PRD: /sites/Analytics/Production/dimensoes
In DEV, I go to Manage shortcut → Edit target → Target subpath, select the variable and save.
However, after saving, the variable association seems to disappear and the shortcut keeps only the resolved DEV path.
When deploying to QA, even though the QA Value Set is active, the shortcut still points to the DEV path. If I change it manually to the QA path, it works.
Is this a known issue with Variable Libraries and SharePoint Shortcuts, or am I missing a configuration step?
Thanks!
Hi DMendes,
Based on the current documentation, I don't think what you're seeing is the expected behaviour.
Microsoft's shortcut variable guidance says that a Variable Library value can be assigned to an individual shortcut property, and after saving the variable name and resolved value should remain visible on that property.
So if you bind the variable to Target subpath, save it, reopen the shortcut and the variable association has disappeared completely while only the resolved DEV path remains, I would suspect the binding itself is not being persisted. In that state, activating the QA Value Set would have nothing to re-resolve.
Since you mentioned that manually entering the QA path works, I would be less suspicious of the SharePoint path itself and more suspicious of the Variable Library binding on that property.
I also cannot currently find this exact behaviour listed as a published Fabric Known Issue, so I would capture the before/after screenshots and raise it with Microsoft Support if the binding consistently disappears after Save.
As a CI/CD workaround, the OneLake Shortcuts REST API can create or update a SharePoint shortcut with an environment-specific subpath using CreateOrOverwrite. That would not preserve the Variable Library association, but it would let your deployment process deterministically set the DEV/QA/PRD path instead of changing it manually after each deployment.
AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.
4 Replies
- v-csrikanth
Community Support
Hi DMendes
We would like to inquire whether have you got the chance to check the solutions provided by ShivekMaharaj in community to resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.
- v-csrikanth
Hi DMendes
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.
Thank you.
I didn't have time to test the solution, I'll let you know as soon as I test it.
Thank you so much for the help ShivekMaharaj
- ShivekMaharaj
Resident Rockstar
Hi DMendes,
Based on the current documentation, I don't think what you're seeing is the expected behaviour.
Microsoft's shortcut variable guidance says that a Variable Library value can be assigned to an individual shortcut property, and after saving the variable name and resolved value should remain visible on that property.
So if you bind the variable to Target subpath, save it, reopen the shortcut and the variable association has disappeared completely while only the resolved DEV path remains, I would suspect the binding itself is not being persisted. In that state, activating the QA Value Set would have nothing to re-resolve.
Since you mentioned that manually entering the QA path works, I would be less suspicious of the SharePoint path itself and more suspicious of the Variable Library binding on that property.
I also cannot currently find this exact behaviour listed as a published Fabric Known Issue, so I would capture the before/after screenshots and raise it with Microsoft Support if the binding consistently disappears after Save.
As a CI/CD workaround, the OneLake Shortcuts REST API can create or update a SharePoint shortcut with an environment-specific subpath using CreateOrOverwrite. That would not preserve the Variable Library association, but it would let your deployment process deterministically set the DEV/QA/PRD path instead of changing it manually after each deployment.
AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.
