Sage 100

Sage 100 v4.4 upgrade to 2013. For one customer on both AP Vendors and AR Customers the ""Customer/Vendor"" Status was NOT flagged during upgrade to ""A"". Instead on both masterfile items the status was left blank. This causes problems if you try to select by status because a blank status won't be selected (for example customer statements). On both the customer databases the file layout for the AR_Customer and AP_Vendor also do not match the order that I see on my 2013 system. So there is some process by which the fields are added during the upgrade/conversion however I theorize that those fields not being in the prior position are causing something in Sage's migration to not work. As part of a test conversion I followed what has been a pretty standard procedure: 1. Install 2013 2. Migrate & convert 3. During go live I just pulled over MAS_xxx and reconverted. I did not go through another migration. It's possible that this step #3 during the 2013 upgrade caused issues. Just an FYI in case you see this on an upgrade. So far the only resolution I've found is to VI into the files to manually change the status to ""A"" which has worked on the AR_Customer (yet to do the AP_Vendor). Very disappointing to go to customers and advise them to ""keep current"" and then these little teeny upgrades (when measured by new features) throw off a boatload of after-upgrade support calls. This simply will not be sustainable for the future of Sage 100.

@WayneSchulz Thanks for the heads up!

It seems this might be something a bored consultant could whip up a script to handle.

@WayneSchulz were they flagged as ""A"" after the test migration?

I did not check after the initial conversion. First time I've run into a situation where the data file layouts were not in the same order as my Sage 100 system.

Hmmm - I took a peek at a couple clients I recently upgraded - one from 4.1, the other from 4.3. In both cases, I migrated data (didn't pull over the company) and re-convert. In both cases, the Status field in both customer and vendor is populated. In the 4.1 client, the field in Customer Maintenance was field 82 (field 74 is a UDF). Vendor master - field is 37. In the 4.3 client, customer master field is 83 (no UDFs), vendor master field is 52. These clients have different modules, and as noted, converted UDFs are not at the end of the file. Both differ from my local install, which is vanilla, non-migrated, and matches File Layouts.

Wayne - out of curiousity why do you not migrate the company files again at go live? I normally migrate company files at go live and have not experienced any issues such as you are describing. I HAVE had Sage support tell it was fine to just copy the company data over and convert when there were problems getting the migration to work at go live.

He didn't remigrate, he only copied and converted (see step 3). I'm wondering if that is why it didn't convert correctly?

I got that he didn't remigrate. That is my question. Why is it his process to not remigrate.

I did not remigrate because I think in some cases it has remigrated users, security, messed up custom reports, forms. For a rather ""simple"" upgrade I've been fairly lucky with this route though on this upgrade something clearly went south. My usual process would be to re-migrate (especially with Paperless -- which I did not have here) though I almost always cringe when doing so. I know there are options to not remigrate system, users, etc but I've had mixed results in some cases. Sage lacks the real-world experience to know that a 50 user site is probably not going to upgrade Sage 100 in the AM and go live in the PM. I'm really curious how this will all work with the new installer once 2014 comes out and may preclude us from easily running two instances of Sage 100 on the same server without a lot of fancy gymnastics. My guess is the academics in Irvine will have many conference calls to try to figure out (again) why the upgrade process is slow on the uptake.

Is there a document out there that lists the steps the migration routine goes through based on what options are chosen? Can someone help us create one? I think we could use this information to decide when or whether to re-migrate as well as a resource to troubleshoot upgrade issues. I have had issues similar to what @WayneSchulz outlined and also Mixed Results. It would be nice to cut down on the Mixed Results.

Attend the ""Sage 100 2013 Upgrade Do's & Don'ts"" session at MotM.....

The last time I had data that looked like it was out of order, Sage had me replace Embedded IO files: Select File, Run. Enter SYZCON in the Program field At the prompt, enter O=NEW(""SY_ACTIVATION_BUS"",%SYS_SS At the prompt, enter PRINT O'ACTIVATE(""y/y"",""xxx"") oy/y = module code (for example: A/R,S/O, C/I, I/M) oxxx = company code o1 is returned if the command was successful o0 is returned if the command failed At the prompt, enter bye

Wow @MaryJoKrueger , you and @JoanSerr know your SYZCON stuff. https://90minds-com.socialcast.com/messages/19376695

Have to admit - I can't say I KNOW it. I just have a pretty good memory and know how to file notes :)