Sage 100

Soon to be upgrading from MAS 90 v4.4 PU 6 with JobOps 4.4 R2. Is it too soon to go to 2014 R1?

We haven't done any upgrades to 2014 R1 yet but we have discussed it as a team and determined that will be our plan for the next upgrade installation where they have JobOps mainly because we have had several version 2013 installations where we had numerous individual fixes that had to be installed. They are good about getting revised programs out to fix bugs but they don't build them into their install files and it's hard to keep track of them.

I spoke with Ryan Rick last week at Summit and posed that exact questions (moving to 2014). They don't have any pioneers that have moved to v2014 as of last week. It ""should"" be ok. Just depends if you want to be the pioneer................

JobOps + Pioneer = ""Hell no!

Kathryn, Did you upgrade to 2014 R1 and if what was your experience? If not...wondering if any others have taken the plunge ? Thanks for any feedback you might have.

I have client on v4.5 JO and CRM. CRM went live back in April and almost immediately started blowing errors in SO entry when linking the SO to the CRM record.. The ""not me"" game started immediately with none of the three wanting to get involved. After a couple months of the crap (problem does not manifest itself if you don't link the lead upon SO CREATION), we finally had a powwow with Sage in July. Another month goes by getting NDA's and files sent to Sage. And get this, problem isn't replicable.............. Now data is being sent to JobOps... Two weeks ago I suggested that we go to v2014, install the latest CRM and see what happens. Can't get any worse can it????

I completed a 4.1 to v2014 JobOps base only customer is not live yet but should be at the end of the month. I had issues with Parallel Migration ""Prepare failed with the following error:"" which then said nothing. JobOps provided two programs SY_Enhancement.M4T and SY_ClasssEnhancement.M4T, that I installed in 4.10 issue was resolved. During conversion, I received Error 121 JT_LevelConversion line 1141 sent 5 programs restarted conversion all was going well... Until I got the error about CC and CI_SageExchange even though they do not have CC installed or stored. I saw a post by @John Leonard and deleted the record in SY_CreditCardRestart the conversion completed. Testing seems to be going well, I have not found any issues yet.

@RebekahVeuger - The client I'm working with is a slow mover, so no real updates yet. Thanks for keeping the thread alive tho. @LisaDion - Great insights for those of us scared to test the waters!

This was provided to me by Tonya O'Neal, a programmer at JobOps. I have a client on v4.5 JO that has been struggling since April when they integrated CRM into the mix. It appears that Sage/JobOps/CRM have identified a sequence of events that creates the havoc. The suggestion from Sage is to upgrade to v2013 or v2014. I asked Tonya about the robustness of v2014 and this was her response. JobOps 2014 has been in the field since mid-July. We do have a couple of hot fixes which are available for download on our website and are accessible from the same location as the software download. We are planning a maintenance release in the next 30 days.