Sage 100

Message received ""Record (0034096001000) is in use by another user"" when trying to access a step in Work Ticket Entry when another user has that work ticket being viewed in Work Ticket Inquiry. Updated programs attached. Version 440 PU7/Nanook R3

is this a typical release for JobOps? Seems to have even more issues than the basic Sage product. One of my clients started the JobOps process in October and they have had several issues related to JO and they aren't even live with the product yet...........

Well........let's just say I run into a fair share of bugs. I support a lot of JobOps clients, and it is typical after installing a new release or product update that bugs crop up rather quickly. Anything I can help you with?

No. JO is not a specialty so I am just a back seat observer right now.

Whenever the Sage release has affected major integrated modules, it has been a challenge for JobOps, and this has been true with 4.40. Also with 4.40, there were some MAS inventory issues we had to deal with in JobOps. As with any type of new releases, testing is critical. With the JobOps R3 release, we feel like this is relatively stable now. Would you agree, Jane?

@JohnHoyt I'm not so sure I agree about stability ... I continue to run into enough bugs (new and old) on every release, no matter how big or small the release. I don't expect software to be bug free, but some of the things that my customers run into suprise me as it indicates the areas weren't tested. WIP continues to be a problem to reconcile, and there are always ongoing data problems as evidenced when running the JobOps Validation Utility ... lots of PO linking problems as well as orphaned work tickets, parent item codes getting captured as ""Item Code"" in the WT header record, cost mismatches, 401's, etc.

Try to avoid inventory valuation changes from like FIFO to serial or lot- lots of challenges there.

Sounds like they have adopted the Sage model of QC. Bang out the code, release the alpha and let the users test drive it for them!

@JohnnyPabian is this a JobOps challenge/problem or Sage's?

We believe it is a job ops - if a PO was linked to a work ticket and valuation changes to a serial before it is received. I think what is happening is the serial number is not hitting the work ticket. Though we have not officially logged a case as we are having to spend so much time trying to determine those exact steps/issues- sage or jobops. Trying to get our ducks in a row to prove either way.

Thanks for the info.