How to find target path of existing shortcut

[fabricator1]

How to find out what is the "original" table or folder that an existing shortcut is pointing to?
(i.e. the target path which an existing shortcut is pointing to)

[fabricator1]

If anyone reads this thread because they have the same need, I have made an idea to make it possible to see the target path of a shortcut: Microsoft Idea

Please vote if you also would like this functionality 🙂

[AndyDDC]

Hi @fabricator1 I'm hoping the upcoming Shortcuts API will expose a way to view this.  In the meantime (and I know it's not ideal) but when a shortcut is created, a connection is created in the Data > Connections area when browsing Settings > Manage Connections and Gateways

[fabricator1]

Thanks! 😀

I am browsing through my list of connections to see if I can spot them.

Will the connection name be a reference to the target location of the shortcut, or to the shortcut location of the shortcut, or (hopefully) both?

Will the connection be of a certain Connection type?

I found some connections which look like they might have been created when creating a shortcut, however I wasn't able to find references to both the target and the shortcut in the connection name, so I wasn't able to nail it down.

Using the lineage view in the workspace can also give clues, if all the shortcuts and targets are inside the same workspace I think. 

I am however hoping for some way to be able to verify 100%, for a certain shortcut, what is the target of the shortcut 🙂 As far as I can see, that info is only visible for me during the creation process of the shortcut, but not after. So for now, I am relying on the naming of the shortcuts to tell me where the target is located.

I would like the target path to be permanently visible inside the properties view of a shortcut (as long as there's no security concern I'm missing here), and through the API 🙂

[AndyDDC]

It doesn't explicitly say the connection type is a shorcut, just the specific connector type to whatever is being shortcut to.  E.G. Azure Data Lake

Yes it's not that easy at the moment.  Going forward I'm adding some useful info to the shortcut name

[v-nikhilan-msft · Accepted solution]

Hi @fabricator1 
We can use the Get Shortcut API to get the path. But this is not yet deployed to all the regions.

You can refer to this link: OneLake Shortcuts - Get Shortcut - REST API (Core) | Microsoft Learn

Hope this helps. Please let me know if you have any further questions.

[andre]

does not help, this link does not work.  This should probably be addressed in a Semantic link library.. it does not make sense to make API call for somethign that's supposed to be available at your fingertips.  How does it make sense to have shortcuts and not be able to see where the data is coming from???