I found this post and was hoping that it would resolve the issue of painfully trying to relink the Paperless Office records after migration. I am in the process of migrating Sage 100 Standard 2022 to Sage 100 Advanced 2024. 32bit PVX versions. This is an on-prem to Azure along with Sage version & edition migration. So far the migration seems to be 100% successful. So I found this utility and ran it and I am a bit confused of the results. At the end it states that Total Records Read: 79634, Total Records Update: 2662. So why such disparity in what was updated. Also, after performing the processing, I closed and re-opened the utility, re-ran the scan, the same original paths still exist in the Search For field. I would have thought that it would now show the paths I had inputted into the Replace With field. Screenshot below:

Review the Sage 100 PL file changes, it looks like it only processed against the PL_Report.m4t & PL_ReportPDFLog.m4t files. The Journal Registers and Period End files would have the most entries, I would think.

One last thing I want to add. When I moved my PDFs from Paperless Office on the on-prem system, I only copied the last 5 years of files to reduce the number of files in the system, It went from 57K+ files to 20K+ files. But the number of PDFs that actually exist should have nothing to do with the file path replacement, correct?

I'm going to try a few other iterations.

First I want to thank David Speck for creating and providing this utility. I hope that he is still monitoring this thread and can provide some feedback, or maybe some of you that have used this utility.

Thanks
Lonnie

Hi Lonnie,

The replacement that occurs IS case-sensitive so double check the casing if the paths in the left column.

Also, the utility will attempt to update paths in every applicable file in a Sage 100 system.  This includes the three possible company and module specific log files for AP, AR, and PR as well as the system log files and the Paperless Office configuration files.

The utility will make a timestamped backup of each file that it makes a change to so you can always restore a file and compare between scans.

Hi David,

Thanks so much for the quick reply. I ran it again, verified my input, and this time it read the same 79634, but updated 56260, which is closer to what I was expecting. And I can see now with the .m4t files that JournalRegister & PeriodEnd files now have copies which indicate they have been updated. Also, post update, when I re-run the scan, it now lists the entries as I expect them in the Search For field.

The above is now correct.

So again, thanks for this utility. Saved so much time, effort, and grief. And thanks for the response.

Lonnie

Hi David,

Thanks so much for the quick reply. I ran it again, verified my input, and this time it read the same 79634, but updated 56260, which is closer to what I was expecting. And I can see now with the .m4t files that JournalRegister & PeriodEnd files now have copies which indicate they have been updated. Also, post update, when I re-run the scan, it now lists the entries as I expect them in the Search For field.

The above is now correct.

So again, thanks for this utility. Saved so much time, effort, and grief. And thanks for the response.

Lonnie