Apr 06 2020 05:11 AM
I ran into a a niche case today where the URL encoding of the "?" character to "%3F" in a SharePoint document link returns the error "Sorry, something went wrong. An unexpected error has occurred." Seems like something that SharePoint should be able to handle...
This occurred when a user exported a PowerPoint to PDF on a Mac. Underlying error though is that the URL Encoded link doesn't work.
Working link: https://{tenant}.sharepoint.com/:x:/s/{site}/{SharingCode}?e=Smsfl2
Failing link: https://{tenant}.sharepoint.com/:x:/s/{site}/{SharingCode}%3Fe=Smsfl2
This behaviour also fails for other links generated by Sharing documents
Can anyone else confirm that they see this behaviour?
May 12 2020 01:21 PM
I am having the same problem. When I export a PowerPoint as a PDF on a Mac with Microsoft Stream links, the ? in the links
https://web.microsoftstream.com/video/5a07a7[shortened]03f65226fd?st=115
Become
https://web.microsoftstream.com/video/5a07a7[shortened]03f65226fd%3fst=115
Which breaks the links
Feb 01 2021 08:23 AM
i face also similar issues with a link which includes a # - when i open the excel in teams directly the link works correct. if i open the excel file in the app the link is broken and navigates me back to the home of the page.
For ppt to pdf creation. the # is removed and i get the same something went wrong message.
It has a huge impact currently by using links to navigate between different applications.
Feb 01 2021 08:33 AM
FYI the above issue stopped being a problem somewhere along the way. Not sure if it was an upgrade to PowerPoint or the PDF component that fixed it on my Mac
Feb 23 2023 01:20 PM
Aug 28 2023 06:05 PM
@kateMenkhaus were you able to find a solution? Thanks!