Sage 100

Job Ops Gurus - Client currently on v4.5 Job Ops. Is the water safe enough to recommend that they upgrade to the latest v2013 release? @DebThomas @JaneScanlan, @JohnHoyt ?? Preparing to do JOScan implementation as well as other major work. and don't want to have to repeat the work. How about v2014??

I have several JobOps clients on 2013 with PU4 ... however, there have been a number of bug fixes. JobOps is going to release PU5 any day now, so I would wait as it will have incorporated into it the bugs that I have posted, as well as others I don't know about. PU5 should be ""safe"" ... .it's not a major release so I would rather see you upgrade to that since 2013 PU4 has been out for quite some time and has several known issues corrected.

I agree with Jane, some Time Time Tracker, some advanced scheduling...I would wait.

The PU5 compliant release of JobOps was released sometime last Friday. I would install that as there are a lot of bug fixes, plus a nice new little feature in CEM.

@JaneScanlan - What is the nice new little feature in CEM??

A new column ... see the attached.

@JaneScanlan - Thanks

Decisions, Decisions. What is the word for v2014?? Have one client on v4.5 PU6 just struggling with weird Job Ops error. Seems to have started about the time they went live with CRM. Trying to track down issue is a struggle (is it CRM related, Is it Job Ops, is it Sage ERP, is it something a rogue script that was installed, didn't work and was uninstalled but still somehow active??). End user is getting pissed and there seems to be no light at the end of the tunnel. So do we cross our fingers and move to v2013? Test the water with v2014 or what? BTW, the issue is with SO entry. Move to tab 3 and an error pops up ""The (blank) is invalid"" Appears to be sales tax schedule related (based on the message. The tax schedule is valid and on occasion, Avalara icon on tab two displays during the pop up. Less frequently, they will also get a message ""You cannot recalculate weight if use shipping code is not set to actual...... If user accepts the order, then goes back, the errors do not recur...... Any thoughts out there (both on moving up and on the errors)???

2014 is not released yet. I would advise upgrading your client to 2013 now ... it is very stable. I have a fix to post which I will be doing shortly. It sounds like there might be an Avatax/JobOps business object issue. I suggest you contact JobOps since the client has Avatax and it seems to be a problem with Sales Tax Schedules.

I knew this rang a bell. Why do JobOps and Avalara seem to have issues? https://90minds-com.socialcast.com/messages/20765453?ref=stream

@JaneScanlan - Just to be clear, client does NOT have Avalara. It just ""seems"" like Avalara is somehow activated in certain areas.

If they don't have Avalara, then there should be no reason for any Ava anything present. I've got dozens of JobOps installations with no Avatax and there is no sign of it being present. It sounds like something Avalara was installed at some point. The Avalara stuff needs to get removed from this system as there is no reason for it to sort of appear in random places ... it's just not right.

I have asked point blank if they have ever installed Avalara and they said no. They sell to distributors so they would have no reason for it.

Getting some engagement from the JobOps folks (finally). Trying a different SO_SalesOrder_bus.pvc. Will report back.

Closer..... Briefly: my understanding from JobOps is that Sage released an updated SO_SalesOrder_Bus.pvc file post PU6 but before PU7 that addressed issues when using Sage 100 with CRM. JobOps, in turn, also released updated files for the same reason. We need to apply the updated Sage file and the JobOps files (already copied to.