Sage 100

Sage 100 2018 is now available for download - https://goo.gl/xdaUS5 If you are an early adopter please do me a favor and hashtag any of your posts on this release as #2018pioneer so that there's an easy way to review early feedback. I'm hoping to implement this quickly for non-PR users and gathering early feedback from a trusted group will make that easier.

Let the games begin!!! VERY interested in the journeys of those brave souls doing a PR migration!!!!

Reminder to all: Please use the hashtag referenced in the main message - I think this will let us gather early feedback and judge when it's safe to start rolling out to customers. Also, 2017.3 was released as well.

We are in process of implementing Sage 100, including payroll for a new customer with > 500 employees and they have decided to just go for it. We are implanting new, rather than migrating from. Hope that is less dangerous. #2018pioneer

Back in the day, part of my implementation kit was a fifth of Jack Daniels. Whenever a problem was reported to me, I would knock a shot down. The implementation went smoother as the day wore on......

Also remember there is no Timecard module at all until PU1 (not as Framework, not as a legacy non-Framework module). It's not on the 2018 installer at all and Migration will stop you but better to plan to delay implementation until PU1 instead of being surprised. Also IMHO too close to year end. Rumor has it Sage is expecting very low adoption rate for 2018 anyway this quarter due to impending year end. Also remember from 4.40 it took several PUs for I/M and P/O to get stable. Recommend strongly wait for PU1 instead of #2018Pioneer. What @JeffSchwenk said too. Side note : The mention of ""Sage mobility for Bar Code"" is a complete misnomer.

It's ALL (not just Sage) beta until PU1...

This new implementation includes GL, AR, AP, BR and Payroll...thoughts on starting off with 2018 for this configuration or sticking with 2017 and upgrade next year?

With over 500 employees? Version 2017, unless you are being paid by the hour and have a good 'hold harmless' clause in your agreement.

@RobertRuff - No guts, no GLORY!!!! Maybe @BethBowers will add her two cents as well or some of the other PR testers in the group. Apparently, there was NOT an overwhelming number of PR guinea pigs from the Sage universe willing to take an arrow or two like a good pioneer. Another thought to add to Moira's would be to contact the Sage development team (Diane.Coffman@sage.com) or someone with clout in tech support (jeff.konstanzer@sage.com or Carmen.Cruz@sage.com) and talk it over with them. I have heard that there are about 15 bugs that were deferred to PU1. Maybe they will tell you about the open issues and/or commit to expedited support if you are willing to your reputation on the line. Hopefully, you don't develop a drinking problem.......

I see no reason to go 2018 since the data will migrate from 2017. I would definitely advise this customer to go to 2017 for payroll and consider a Q1 or Q2 upgrade to 2018. There seem to be quite a few changes to how you'll use VI w/payroll. I would not want to be debugging VI as well during a payroll go live. My price to go 2018 would be substantially higher and would have a written clause that I advised they wait for the first PU at least. 500 employees is not something to toy with.

Here's a partial list of things that were not working for one of my brave souls. I don't know if it was the last beta or the final release, but there probably wasn't much diff between the two, anyway. 1 - Check History file does not list vacation hours. 2 - Quarterly tax report not working correctly for employees who live in one state, work and pay taxes in another (we have an apparently special case in Indiana - no matter where you LIVE, if you work in IN you pay county taxes to the IN county - not like a reciprocal where you get it back as a refund later - you PAY THE TAX). 3 - Employer's Expense Report - no detail on local taxes and incorrect earnings on one of his depts 4 - Earnings/Deductions reports don't appear to have converted data, only have new data (so YTD incorrect) 5 - Qtrly Pay Recap Report - SS earnings incorrect (although it's correct on Qrtly Tax Report), 6 - Various AAtrix issue with the IN county thing, 7 - Employee Maint/Tax Summary - WH line appears to be W2 INCOME Amt In other words - REALLY, SAGE?

Aaaaahh, Payroll 2.0, brought to you by the makers of Sales Order 4.1...

OMG, @PhilMcIntosh - PLEASE do not mention SO 4.1 ever again. I still have nightmares over that.

Those who cannot remember the past are condemned to repeat it.

Yes, the reseller Beta Bunch worked SO Hard on that release and it appeared we didn't even scratch the bug surface when it was released. I almost sent my beta certificate back to George and Erika.

#2018Pioneer : My coworker installed 2018 in the last couple of days and also using the Crystal posting from Wayne. Her email to our team: I installed Sage v2018 to my computer, uninstalled Crystal Reports 11, installed the new version of Crystal, copied a file from the home directory from v2018 to v2017 (recommended by Schultz Consulting). My v2017 was freezing and not operable. I uninstalled Sage v2018 and the new version of Crystal, reinstalled Sage v2017 and related products to get me back to square one. I spent hours on this. After I asked her if I could post this, she agreed and also came back with a notation that her 2017 had Job Ops installed but did not install with 2018 but didn't feel that should have caused a problem. This morning I heard this are Payroll bugs in 2018 too.

JobOps isn't yet compatible with 2018, so how could anyone say they ""didn't feel that should have caused a problem""?

@JohnHoyt, JobOps was installed on her 2017, I don't believe she migrated data, just installed 2018 (with no JobOps).

OK, that works.

On my relatively fresh install of Sage 100 Standard 2017.3 which is on my laptop with Windows 10 1709 - I installed Sage 100 Standard 2018. This is what I found. - I did **not** already have Crystal 2011 installed - I did **not** install Crystal 2016 - I do **not** have Job Ops on either 2017.3 or 2018 - I was **not** able to test over a network since I have everything here in the cloud and don't use a local network in the office - so my testing was all on install locally to laptop - Once I installed 2018, when I went into Sage 100 Standard 2017.3 I was able to open the program normally. No errors. - I navigated to GL on 2017.3 and went to account maintenance without any errors. I went to print a GL account listing to preview. - From the 2017.3 preview, I received the **Unable to cast COM object of type"" when printing in prior Sage 100 versions after installing Sage 100 2018**. - Followed the instructions https://goo.gl/d5VG9M - Went back into 2017.3 and observed that the error went away when trying to preview a GL account listing I did not exhaustively test every permutation of Crystal Installed / Crystal Not Installed / Crystal Not Originally Installed but Crystal 2016 installed with Sage 100 2018. I also would not rule out a Job Ops issue with migration to 2018 (though I wouldn't expect this to impact 2017.3) even if data was not selected to migrate there may be Job Ops system files/forms/custom panels/UDFS which get migrated (pure guess on my part). I suspect that there are likely other issues at work which may/may cause problems with 2017.3 during the upgrade to 2018.