Forum Discussion

asifkhawaja7's avatar
asifkhawaja7
Copper Contributor
Mar 10, 2025

Best Way to Generate Durable Document ID Links

Hi everyone,

The purpose of the Document ID feature in SharePoint is to create durable links, but what is the intended way to generate and copy those links efficiently?

Most common link creation methods such as the "Create Link" button in a SharePoint record still generate path-based links even with Document ID enabled. Even using the Document ID column doesn’t provide a direct way to copy the Doc ID URL, as clicking it simply redirects back to a path-based link.

The only way I’ve found to copy a Document ID link is:

  1. Go to the SharePoint library
  2. Right-click the record
  3. Open the details pane
  4. Right-click and copy the Document ID URL

This method is cumbersome and impractical, especially for synced files. As a result, users will likely default to copying path-based links, which defeats the purpose of durable Doc ID links.

Has anyone found a better way to easily generate and copy Document ID links without extra steps? It seems like this issue has been raised for years without a proper solution.

Thanks!

3 Replies

  • JamesHogg's avatar
    JamesHogg
    Copper Contributor

    $300B revenue company and noone in it has realised that they are costing the world economy trillions in lost productivity trying to locate documents because they were renamed in SharePoint and that broke some filepath sharing link that no web app has ever used. Obviously the problem when have devs migrate from a Windows file path world and don't have any accountability for the product they are producing as it is only used because it is "free" within the bundle. 

  • JamesHogg's avatar
    JamesHogg
    Copper Contributor

    $300B revenue company and noone in it has realised that they are costing the world economy trillions in lost productivity trying to locate documents because they were renamed in SharePoint and that broke some filepath sharing link that no web app has ever used. Obviously the problem when have devs migrate from a Windows file path world and don't have any accountability for the product they are producing as it is only used because it is "free" within the bundle. 

Resources