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;
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.