Currently, the Paperless Office log files can not be accessed through Visual Integrator import. Converting from other systems, migrating from SQL, merging companies, changing comany codes, or just because -- it makes sense to be able to import into these tables.
by: Robert W. | over a year ago | Integration
Comments
You cannot import the system settings that are done in the Paperless Office setup
BUT you can import the Customer, Vendor and Employee data that tends to be the most time consuming.
Use AP_VendorDocuments, AR_CusomterDocuments and *PR_EmployeeDocuments. See KB 510500 for details on importing customers.
*PR_EmployeeDocuments does not appear in the VI table list and must be manualy typed into the 'Table Name' field
Chris, Thanks for the information.
Robert, FWIW, I haven't tried an import but on 4.40.0.3, I am seeing the Journal, Period End and Report logs in VI.
It would be great to have a function that would allow you to import a PDF in to the Paperless Office system directly. So when a user makes the mistake of printing a journal to paper rather then PDF you would have a way to scan the document and load it in to the paperless system for continuity.
yes
When migrating Sage to a new server if you have subdirectories it is very time consuming and SLOW. It takes me longer to migrate the paperless office than to do the install and all data conversion
As of Sage 100 2016, Product Update 2 it is currently NOT POSSIBLE to import into PDF Log files such as:
AP_VendorPDFLog.m4t
AR_CustomerPDFLog.m4t
PL_JournalPDFLog.m4t
PL_PeriodEndPDFLog.m4t
PL_ReportPDFLog.m4t
PR_EmployeePDFLog.m4t
These files hold records used by Paperless Office Viewers and the Link Maintenance utility. When companies are restored from backup or migrated and converted, or when PDF file storage locations need to be reorganized or change to a different server, there is a great need, because some customers have tens of thousands of records in these files.
The Link Maintenance utility is sometimes not a viable option because just loading the screen can take a long time (especially if the original storage location is no longer accessible on the network or has been decomissioned), selection can take a long time (hours), and changing links manually can take a long time. By a long time, this can be several minutes to half an hour each time.
When you delete a company and recreate it a new company id is assigned in the system. The Paperless docs are linked by the company id. With a new company id, you cannot see the pdf's even if they are still stored on the system.
There is no utility to re-match the Company Id to the new one.
If you do as advised in Sage Article 44992:
As a last resort, consider deleting the destination company code and its data (this is generally safe, since the destination company code's data would be overwritten anyway), then re-creating the destination company code, and trying to copy again.
Note: For more information, see the Related Resources section how to delete a company code and all of its data.
Note: There are some conditions where this "last resort" is not an option:
If only one module's data, or some modules' data, is being copied, while leaving other modules' data in the destination company code intact (such as if the destination company is a live company and a particular module is being restored). This is because deleting a destination company clears all data from that company.
If there are special system settings (such as in SY_Company.m4t, SY_ReportSetting.m4t and SY_ReportOption.m4t) or custom reports storage, or customized task windows, or other company code specific records, etc. that need to be retained. Copying another company's data into a re-created destination company code may not restore that.
You will loose all references to your PDF files!
We either need a utility to fix the company link or access thru VI to change the records!
Also, if there are numerous records (say, 100,000 records), it is possible in Link Maintenance Utility to encounter an error like "Workspace memory has been exceeded."
Please please please allow us to import into these files. Being allowed to export does not help us. Do you have any idea how much time it takes to get all the PDFs changed to a new path for a new server? This issue is of high importance.