Interesting post. I had this situation today. A couple days ago, I migrated most of the client's v2017 companies to v2020. Today, when fine tuning the paperless logs (moved to new server as well), I realized that I left an archive company behind. So I created the company and activated the modules. I renamed the MAS_XXX folder, then copied the v2017 MAS_XXX folder to new installed.. Everything looks great...... except the paperless log is still missing the PDF links.
DFDM'd the log table (PL_JournalPDFLog.M4T) and noted that the key is comprised of the company KEY (0000000001). I then looked at the sy_company.m4t. The company KEY 0000000001 was not there and the newly created company code key was 0000000021.
So my question is "what if I rename key 0000000021 to 0000000001 and delete the old key in the company table????? I am a little hesitant because of the encryption data in record 55.
As they say "no guts, no glory". Can anyone think of a
NO NO NO situation? Is the encryption key going to interfere? The migrated data looks fine. My alternative would be to track down an MD to convert the company KEY reference in PL_JournalPDFLog.M4T?
Thanks in advance.
------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------
Original Message:
Sent: 03-22-2021 11:40
From: Kevin Moyes
Subject: Parallel Migration 4.50 To V2019
Make sure the two systems have the same data dictionary (UDF's / UDT...) then copy in the MAS_### folder, create the company code manually and do company conversion. This will throw off things like user key (who created SO / posted invoice...) in the copied company, but I don't know of a way to avoid that.
Yes, you'll lose all related system data like Paperless but the folder copy / convert "should" work.
------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------