Lakehouse shortcuts do not persist variables from Variable Library (Connection, Location, Subpath)

Echoing this one. 

When we open Manage shortcut, choose Edit target, and select a Variable Library variable for the shortcut, the selection appears correctly in the dialog. However, after clicking Update all variables and saving, the assignment is not retained; reopening Manage shortcut shows the previous target configuration. In our case we are attempting to use a mirrored db as the item and path.

Expected: the selected variable remains assigned after saving.

Actual: the selection appears accepted but does not persist. This has been reproducible for about three days.

Steps to reproduce: open a lakehouse with a shortcut, Manage shortcut, Edit target, select a Variable Library variable, Update all variables, save, reopen Manage shortcut.

I am experiencing the same issue.

I have Lakehouse A, where table shortcuts point to tables in Lakehouse B. I am trying to parameterise the Target item using a Variable Library variable of type Item Reference.

I can select the variable successfully in Manage shortcut → Edit target → Target item, but after applying/saving the change, the variable binding is not persisted and the existing Target item value remains.

Interestingly, I have older shortcuts in the same Lakehouse that were created a couple of months ago. For those shortcuts, I was able to assign the Target item using the Variable Library, and those shortcuts still correctly show the Variable Library binding.

So in my case:

• Existing older shortcuts with Variable Library bindings still work.
• New shortcuts do not retain the Variable Library binding.
• Updating existing shortcuts to use a Variable Library variable also does not persist the change.
• The Target item variable is of type Item Reference.

Quick update / Workaround

In case it helps anyone, I found a workaround since my workspace is already connected to Git.

I opened the Workspace in VS Code, edited the JSON file for the shortcut, and updated the Target Connection, Target Location, and Target Subpath values directly there. After syncing and committing the changes, everything was properly reflected in the Lakehouse Web UI.

So the issue is definitely isolated to the Fabric web UI, where assigning or editing variables for shortcuts still doesn't save at all.

Same issue here. 

Trying to use the variable library connection id for my lakehouse file shortcut.

It's quite a fundamental feature. I'm surprised its a standing bug.

I raised this with Microsoft a couple weeks ago. They're aware of the issue and are working on a fix for it, expected to be released in the last week of October. 
The workaround MattDL​ suggested is the same one that Microsoft provided me, and does work.