Open Adobe PDF in client application
Office 365 / SharePoint online needs to support opening PDF documents in SharePoint directly to client application (Adobe Acrobat Pro/DC).
As of this request, technical support has stated the only way to open PDF files in Acrobat is to download/save them.
SharePoint On Premise has supported this feature for some time.
Adobe PDF files are as common and Microsoft Office Suite documents and must be editable directly to/from SharePoint Online without the need to down/save edit, and upload which adds user overhead and lowers productivity.
Thank you everyone for your feedback on this item. We recognize this is a valuable feature and are looking at ways we can address it. We do not have a timeline to share at this point.
Patricia Mueller commented
DAEMON Tools Pro 8.3.0.0759 Crack Free Download 2021 Daemon Tools Pro 8.3.0.0759 Crack is the professional-grade software with an intuitive and notable user interface. This… https://softpediacrack.com/
please can Microsoft make it possible to open PDFs direct in our desired apps from Sharepoint.
We've all been very good girls and boys.
It will save us thousands of hours and stop lots of people getting quite cross !
We use the e-signature function daily in our department. Having these open in Adobe and directly link to SharePoint is totally invaluable. At this time, our browser cannot default to Internet Explorer, which is creating massive problems for us while trying to e-sign stuff in SharePoint.
Thanks, I agree Cory!
It's a post from 2016(!) and nothing has happened.
Yes, please add this feature. I work with PDF files everyday, and need to be able to edit them in Acrobat Pro. Downloading, editing, and then re-uploading to SharePoint and overwriting the old version is a big headache.
This would be really useful. Most users are
on Edge/Chrome and there should be an option to open in App and not browser
we need this feature to open in the default application e.g. adobe reader, we should be able to check the document out, view/amend/sign with the application and check back in.
Open PDF in associated desktop app, Bluebeam in our case.
It is a must have! Many of our businesses are requested this feature. Please make it happen :)
Every vote must be counted!
we need this feagture
Erol Kanik commented
A must have!
Four years on and still no solution - come on Microsoft, this would be much more useful than all the 'major change updates' you keep putting out!
I vote for this
+1 on this. Both for desktop Adobe App and for BlueBeam PDF App.
D. Jäger commented
Conclusion after more than 4 years: Microsoft is not interested in the concerns of users.
Even if I could, I would never allow myself to do it to my customers.
Make Microsoft great again ... but they don't listen.
Tomasz Szałaj commented
Microsoft - you are so arogant with your "no timeline to share at this point". It was easy to cut your competition and it's soo hard to step back when your customers ask you for better solution from your competitor. Shame on you.
i vote for this
Crazy that this hasn't been fixed. We are currently going through the process of considering whether to move on to sharepoint, but as a company that relies heavily on PDF documents, being able to use the functionality of Acrobat, this could tip the balance away from SP
I cannot believe this problem has not been fixed yet.
As an admin, if I choose to configure my sites to allow a document to be opened in its associated client application, then when a user clicks on that PDF, I expect it to open in Adobe Reader. There's no warning on that configuration setting in SharePoint that says "ha ha, don't bother choosing this - it doesn't work."
One of the biggest problems I find with this feature being broken is that the only way for the user to be able to open these PDFs in Adobe Reader is for the user to download the file. This completely negates the whole purpose of a shared library where the only true copy of a file resides in the SharePoint library. Now all of my users will have that file downloaded on their workstations, and if I need to update that file in the library, they most likely won't know about it and will continue to use the outdated copy on their workstation. This is just plain stupid inefficient document management.