Forced to save as in sharepoint online

[koensterken]

Hi everybody,

At the beginning of this year, we purchased a thousand PDF X CHANGE Pro licenses so that we can open PDF files directly from Microsoft SharePoint Online. This would allow us to complete our document workflow as we sign our documents via PDF X CHANGE.

However, PDF X CHANGE forces us to click "save as" when signing a document. We are then forced to first save the signed document locally on the computer and then upload it again. In this way, the PRO version has no added value for us and we are forced to look further.

But maybe there is also a solution, could someone on this forum maybe help us further?

[Paul - PDF-XChange]

Hi koensterken,

thanks for the post. The Pro bundle does indeed have tools to "Open in PDF-XChange editor" and save back directly to SharePoint Online, yes, but it does require a little set up.

The PDF-XChange PRO suite includes integration of the PDF-XChange Editor into SharePoint Online such that users can, when browsing a SharePoint Online document library in any supported Chromium based web browser, (The Edge, Chrome, Brave etc) take advantage of the "Open in PDF-XChange Editor" functionality we offer.

The Editor will open the PDF using the SharePoint tools like Check out/In etc, and on save will be saved directly back to the SharePoint location, so no local saving required.

OpenInEditor.png

In order to take advantage of this functionality one needs:

• License
  A licensed PDF-XChange Pro installation on the machine being used to browse the document library. The functionality is a PDF-XChange Pro premium feature and a valid PDF-XChange Pro license is required.
• Server Side App
  Our server side application installed on your SharePoint Online tenant. This can be found in the SharePoint Store when searching for "PDF-XChange"
• Browser Extension
  The Pro version of PDF-XChange Chromium Extension in your web browser. The PDF-XChange extension found in the various extension repositories for Chromium Browsers does not include the required components to integrate into SharePoint. The PDF-XChange Pro installer will by default put this additional extension functionality in your browser during the PDF-XChange Pro installation process. Installing the browser extension from repositories is not sufficient.
• Local Part
  The "local part" of the tool. This is a component that gets installed on the user's machine by the PDF-XChange Pro installer. It has the role of passing the file properly to the Editor in a fashion that allows use of the SharePoint tools for check out/check in etc.

Server Side App

Get the Server side app from the SharePoint Store by searching PDF-XChange. Note that this is a server side app in the SharePoint Store, not the PDF-XChange Editor published in the generic Microsoft Store.

SharePoint Store.png

should return something like this:

PDFX_App.png

Install that on your SharePoint Online site. Or, if you reach out to support@pdf-xchange.com we can deliver is as a package you upload and install. Both result in the same thing.

Browser Extension

Run the latest installer for PDF-XChange Pro license on the target device to install the complete Browser Extension. Again, the Browser Extensions available in ithe various Browser stores does not include the SharePoint Integration functionality. It is only available via the PDF-XChange Pro Installer.

Local Part

This is also done by the PDF-XChange Pro installer.

Conclusion

The Browser Integration between PDF-XChange and SharePoint requires the server side app and a local PDF-XChange Pro installation.

The 64 bit MSI installer for PDF-XChange Pro is here: https://downloads.pdf-xchange.com/ProV9.x64.msi

I hope this helps. Do let me know how this goes and please do not hesitate to ask if you have any questions with any of this.

sincerely

[Shumous]

Hello,

The above solution does not seem to solve the problem. Having done all the steps above, we do still encounter the same problem.

Is there another solution for this problem?

[Paul - PDF-XChange]

Hi Shumous,

thanks for the feedback. Do you have this set in the Editor preferences?

image.png

That should force it to save directly back to SharePoint and not locally. Do let me know if that helps?

warm regards