You are here: User Guide for PaperSave for Dynamics GP > Integration of PaperSave within SharePoint

Integration of PaperSave within SharePoint

One of PaperSave's greatest strengths is the ability to associate documents to records in a host application (such as documents associated to invoices, customers, orders, gifts, etc...). This provides many advantages. One of the key advantages is the fact that once a document is related to a host application record, it is accessible from the user interfaces within that host application where one would typically look up that record. However, this is not a facility that is available to users within the organization that do not have access to the host application. Typically an organization only licenses users of the host application for only the staff that needs to use that host application on a daily basis. This creates a problem in cases where it may be important to expose documentation that relates to records in that host application to users that may still need to see the documentation but for which the organization does not want to purchase a license for the host application for.

 

Before, PaperSave’s integration with SharePoint required a tight coupling of PaperSave and SharePoint’s backend. Document content was stored in SharePoint while most of the document’s attributes and properties were stored within PaperSave’s database. Some meta-data and permissions were replicated in both locations to ensure a consistent experience from the SharePoint side. There was significant maintenance and overhead in maintaining such a tight coupling of the applications.

 

This was done to support two primary functions SharePoint provided to PaperSave’s users.

 

· The ability for non-host application users to access host application related documents.,
· The ability for any PaperSave user within any PaperSave search interface to search against the content of documents.
· The ability to version documents and check them in and out maintaining version history.

 

In PaperSave 6.0, we now provide these functions without requiring content to be stored in SharePoint. As a result, we are removing support for storing content within SharePoint. Before upgrading to PaperSave 6.0, users are required to move their content from SharePoint back to PaperSave.

 

The pre-requisite checker provides guidance on how to move your content stored within SharePoint back to PaperSave's SQL server database. Review the detailed steps in this article.

 

We added support for native content indexing and search within PaperSave 6.0’s simple and advanced search mechanism to help users search for words found within the PaperSave document content. PaperSave no longer relies on content being stored in SharePoint to support searches against content. Please refer to this section of the guide for more information on native content search and indexing within PaperSave.

 

PaperSave stores all its document content, metadata, and configurations exclusively within the PaperSave database. Prior versions of PaperSave allowed for content to be stored within SharePoint Document Libraries. If you are an existing PaperSave Customer with a version that is older than 6.0 and are storing your Content within SharePoint  (If you are using PaperSave’s integration with SharePoint then you probably are) then that content will need to be moved back to PaperSave’s SQL Server Database prior to your update to 6.0. However, PaperSave provides an ability to configure PaperSave Web Part within SharePoint and perform actions as follows:

 

1. Add Document

 

2. Show Documents

 

3. Show Associated Documents

 

4. Search Documents