Forum Discussion
'Copy Link' for Folder/Files does not work in Teams
- Jun 14, 2022
Great
It works for me as well!!!
Strange thing is mine updated 8th of june but only today it workedYesterday I thought, how can this still be possible as I had this issue for a very long period of time
(opening the Team in SharePoint the copy link always did work as workaround)
but happy now 🙂
Today, instead of an ever spinning wheel I got served with an actual error when I click on the 'Copy link' in the ribbon of the Microsoft Teams Windows Desktop app on the root folder 'Documents/General'. When I click on 'Copy link' on a sub folder or selected file of 'General' I get served with the SharePoint link. But no Teams link anymore...😥😥.
Click on 'Show detals' ;
Click on 'Copy' ;
{"innerError":{},"name":"GraphError","correlationId":"47e30ea0-d0d2-3000-872d-7b0b3139dd1e","isExpected":false,"code":"tooManyResources","extraData":{},"response":{"error":{"code":"notSupported","innerError":{"code":"tooManyResources"},"message":"The request is unprocessable because it uses too many resources"}},"status":422,"serverStack":"","request":{"requestUrl":"https://gs1nederland.sharepoint.com/sites/IT/_api/v2.0/sites/root/items/11a7211d-6bed-49f7-8304-65d5847c8962/driveItem/createLink?ump=1"},"error":{}}
In text:
{"innerError":{},"name":"GraphError","correlationId":"47e30ea0-d0d2-3000-872d-7b0b3139dd1e","isExpected":false,"code":"tooManyResources","extraData":{},"response":{"error":{"code":"notSupported","innerError":{"code":"tooManyResources"},"message":"The request is unprocessable because it uses too many resources"}},"status":422,"serverStack":"","request":{"requestUrl":"https://gs1nederland.sharepoint.com/sites/IT/_api/v2.0/sites/root/items/11a7211d-6bed-49f7-8304-65d5847c8962/driveItem/createLink?ump=1"},"error":{}}
Screenshot after click on 'Copy link' when a sub folder or selected file in 'General' is selected;
- Paul_IQPCDec 21, 2021Brass Contributor
Florisz Henry Edwards Hi all - I can see that the links now work to Sharepoint but does not open the link in Teams itself


. Does anyone know if this is actually possible. I do not particularly want to direct users from Teams to SharePoint, it will just serve to confuse them moving from Teams to Sharepoint and then back again.


For example when I copy a Channel link, I get a link to Teams e.g. https://teams.microsoft.com/channel/etc.. however when I copy a folder in a channel I get a link to SharePoint e.g. https://awspls.sharepoint.com/etc - I would really appreciate any suggestions on how to overcome this if it even possible.
cheers
P
- NBelhamDec 21, 2021Copper ContributorAs per the initial reporter, in the Teams desktop this functionality appears to be broken for some.
- Paul_IQPCDec 21, 2021Brass ContributorNot helpful as you did not read my question. I can open in sharepoint but i do not get a link to Teams. The original reporter reported no link at all but thanks
- NBelhamDec 21, 2021Copper Contributor
@Henry Edwards Florisz for me the problem still exists. After about 60 seconds, the initial dialog grow in size but no detail is displayed. That just remains for more than a couple of minutes.
- BShipeDec 21, 2021Iron Contributor
I'm encountering this issue as well on my current workstation in the Teams desktop client. My workstation exhibits the same behavior in your post where it'll sit, continue to try and load the Copy Link dialog, get larger, and continue to load forever. I've attempted to clear both the Teams cache and browser cache.
Here are my other observations:
- Copying a link in SharePoint Online works as expected.
- Copying a link in the Teams browser client works.
- From a test VM, I was able to open the Teams desktop client and successfully copy a link.
- NBelhamDec 21, 2021Copper ContributorSurely we cannot be expected to clear out of client cache rubbish which break client side functionality! I tried that some days ago and it still didn't work for me. Annoying!
- RobertC20Dec 21, 2021Copper Contributor
For me it's working again.
I don't get an error but the links again. Glad it is solved.
From an IT point of view it is still weird that I had this issue and colleagues did not.