- #Unable to open attachments in outlook 2016 from sharepoint how to#
- #Unable to open attachments in outlook 2016 from sharepoint pdf#
#Unable to open attachments in outlook 2016 from sharepoint pdf#
There are many Legal, Government, Finance and Banking organizations that have learned to work this way, leveraging PDF documents in SharePoint libraries allows them to meet their regulatory requirements and provide a robust end user experience. As a result, our major upgrade is turning into a painful downgrade.
#Unable to open attachments in outlook 2016 from sharepoint how to#
They have no way of knowing how to browse to a document, even if they could set up the Online Account to get them there. They are accustom to the features of SharePoint, specifically folderless views. The Online Accounts option provided in more recent Readers is insufficient for our users, it adds to many steps and for most of them it is too technical anyway. As customers, we are stuck in the middle. It seems that Adobe is not addressing it satisfactorily either. We did take this to a Microsoft Engineer and he tells us that MS's position is that this an Adobe problem. Timoth圜aldwell-2676 at 10:29 AM I'm not impressed with 'community expert' if you are not going to read the whole question. This impacts nearly 2000 users in a single application, there will be more as we get further down the road. Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total. I'm really not sure what the point of it is.Īs we migrate from SHP2007 to SPO, we now have this same issue and have not been able to find an adequate solution. I have it and it makes no difference in the case that I outlined above. Perry.Fiscus - the " Acrobat SharePoint OpenDocuments Component" doesn't help matters at all.
Allow users to disable that warning perhaps, but Adobe needs to take responsibility for the fact that they're really misleading the user into thinking the changes are being saved back up to SharePoint when in fact that is not the case.Īgain, how certain are you that this is a Microsoft issue? I can't believe Adobe hasn't addressed this issue.Īt the very least, it'd be nice if Acrobat could provide some sort of warning that the user is saving to a temporary directory when they choose Save since it's quite unlikely that anyone would ever want to do that anyway. In reality, they've only saved the change to a temporary folder that will ultimately clean itself out. For some reason, Adobe Acrobat downloads the file to a local temp directory (forgetting altogether that it came from SharePoint) and when the user hits Save after making their changes, they close the document thinking everything is great. Any Office applications are conscious of the fact that this document came from a SharePoint link and when a user click Save, the document will be saved to the same location it was opened from. We browse to SharePoint using a web browser and click on the linked documents to open them up. Adobe apparently wants everyone to work directly from Acrobat, but that's just not how 99% of people work.
Are you sure this is a Microsoft issue? Some of us have been struggling with this issue for far too long now.