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.
This is a huge pain in the arse as I load up pdfs onto temp drive to read them in Adobe ! Sort it out!
We have users that have PDFs with attachments embedded into the PDFs. MS Edge browser does not support attachments in PDFs, so we REALLY need the option to open a PDF using the client, directly from SharePoint Online.
Users find the current process very difficult and are thus not properly saving files back online. SharePoint cannot SHARE effectively if the system does not have such basic functions and users circumvent the system. Please address this issue.
Jayakumar ( Hetero IT) commented
we are looking for this Online Sharepoint PDF view literally for organization
We need these feature ASAP. Cant believe these feature is taken away in SPO, its most used feature and now cant perform digital sign for PDFs directly via web version, need to download them but if we download if form have required fields, OneDrive cant sync it and will open in read-only format.
SixPointSteve wrot on· 17 juni 2016 17:15 ·
Agreed that PDF files and SharePoint integration should be as important to Microsoft as MS Office files. The optimal solution is whether accessing PDF files through the browser, mapped drive or Acrobat Online mapping the experience should be the same. Open the PDF file through Acrobat with SharePoint Integration features enabled, Check-out and Edit, Open, Cancel buttons. If a version of Acrobat is not available, then open in Acrobat Reader. We can discuss the SharePoint Integration buttons and features another time.
Still no solution for this issue which is still a real pain for a lot of users.
This does really feel like Microsoft likes to use their own documents and does not want a good support for PDF. But without good support of PDF the opportunities for sharepoint, edge and internet explorer are missed.
Stuart Deane commented
Very frustrating please fix this SharePoint team - Love SharePoint but this is a real pain as our school deals with PDF files constantly...
The Open in Browser might get it into Acrobat, but if you do something like annotate and then save it, it doesn’t save back to SharePoint. It wants save to your Adobe Cloud or local drive. Unusable. I spoke to both MS and Adobe at Ignite last year and both were clueless about it being a problem. Do they even use their own stuff?
Peter Markwell commented
It's not even consistent.
If you click on the title of the PDF document, it opens in the browser, which is no good for many of the reasons mentioned here already.
But if you select the checkbox for the file then go to the open->Open in Browser option at the top, the browser and system settings are respected and the pdf is opened in the system defined reader, FoxIT or Adobe Reader or whatever it's set to.
Ian Hornsby commented
absolutely agree. any kind of collaborative drawing management relies heavily on PDFs for markup. The workaround is to use OneDrive to get the PDF to be local and open in the local Client App (Acrobat DC), and let OneDrive re-synch back to SharePoint … ok until another OneDrive user does the same, and then you are back to file duplication conflict - a second file is created, and any complex metadata/workflow against the original does not relate to the second (2) version … highly frustrating and workplace-inefficient
Mary Nottle commented
Yes, please add this functionality - it's killing our SharePoint Online implementation. Particularly, the benefit of collaborating in a document in SharePoint Online.
Jamie Gillett commented
This is proving a major hurdle for our migration to SharePoint, could someone from Microsoft please respond to this requested feature.
Geraldine S commented
At this stage the only way I have managed to edit pdf files has been to sync the library to File explorer and users then can edit the files opening them in their pdf writer (in our case Bluebeam). However, ideally we would like for users to be able to edit in browser as it will help with adoption and small edits.
Yes, please add this functionality.
Totally agree..... this is an ongoing problem & is causing a BIG downfall within our agency to use SP utilizing .pdf files.
Please address this issue asap!
This is so frustrating and needs to be fixed.... adding my vote!
I am confused by the recent Adobe-MS "partnership" announcements. The official posts do not address this issue directly. Currently, we have to check out, download, edit, save outside of SPO, and then upload-replace pdf files in SPO as the only method to edit PDFs. The official posts seem to imply that we can now edit directly in browser...we simply need to convince our companies to pay for additional Adobe services (and have IT certify Adobe cloud) in order to do so.
Why are SPO and Office web apps so slow to adopt features its competitors adopted years ago? I get that Adobe has a stranglehold on PDF, even though it's original use (print only/scans) is no longer feasible. However, forcing MS clients to use file shares and local storage to edit cloud files of a certain file type is not a responsible strategy and shows how MS is still not client-focused. Furthermore, the fact that new features are supposedly rolled out to cloud platform faster than on-prem, yet we can only edit and open PDF files in Adobe client if stored on-prem.
So, when can we expect to see GDocs style concurrent multi-user text cursors in MS web apps and when can we expect, if ever, to be able to open and edit PDF files stored in Adobe client that are stored in SharePoint Online?
Bill Burke commented
Over 3 years this has been open. They don't care
This functionality is a definite need for users!