Friends! Any votes are appreciated to fix my WIP issues. If we transacted correctly every time, it wouldn’t be needed, unfortunately, that’s not meant for me 
Supported Way to Fix Broken / Missing WIP | Epicor Ideas Portal
My idea for the day: Auto Close jobs on receipt
I implemented this via a BPM in the past, but would like to make it core in the future. this saves a lot of time and frustration. Automatic closing of a job upon FULL RECEIPT of the job. Note that it examines all activity on the job to make sure that there are no open materials, operations, POs, Receipts, Inspections, Labor, etc, and if everythign is perfect, simply completes and/or closes the job.
Allow Simultaneous Quantity Reporting from MES
Back in Epicor 10.2 you could have multiple employees report quantity against a job operation without any issues. All the related tables like JobOper and ResourceTimeUsed would get updated correctly with the values from both labor details.
Starting some time in the Kinetic days, tables like JobOper only get updated with one of the entries. If two employees report quantity, the QtyCompleted field (and others) get out-of-sync with the labor details.
This is “fixed” in 2026.100 so one of the employees will get a generic error message now…No message about retrying the transaction or any indication that this is something that’s expected.
This all came up while trying to dig into why data wasn’t being updated correctly from MES: Reporting Quantity from Multiple Workstations
Hey @timshuwy
Who do we need to complain to about this pending “fix” which is not a fix, but a bandaid that will break lots of automation?
There needs to be a real fix. The proposed fix is worse than the bug. The bug was one clobbered calculated field. The fix will throw bs errors.
How about we just finish all the work in a locking, thread safe fashion like one would expect?
well, you can complain to me… but that just adds ammo to my discussion that I started when I read this idea several days ago. I dont like the “fix”.. but this fix is not new. it was done sometime during the migration to Kinetic. I am working on it.
No, there is no “fix” currently.
Everything works except the JobOper.QtyComplete field is clobbered if reportQty is concurrent or close together.
The proposed “fix” is to throw an error, instead of fixing the underlying problem.
And this supposed “fix” is supposed to be in 2026.100. I’d like it to never get there lol.
Now where is that idea to just put on the brakes again? LOL Lets cut the change and focus on stability please.
we cannot “stop” everything… but we did slow down a little this past release to resolve some browser issues for 2026.100, as well as our retooling for CI/CD release structure for Kinetic. things will start accellerating again soon.
I just think many would prefer you guys slow-the-roll on new until 2027.100 at least. Make 2026.1xx.xx be mostly about stability and bug fixes, remaining parity issues and get the kinks worked out of your CI/CD processes.
I didn’t find any Frideas topic for May 8 so I will put it here.
Add an option to disable striped rows (zebra | Epicor Ideas Portal
Zebra striping improves readability but can conflict with conditional row coloring (e.g. status-based colors). When both are active, users may confuse decorative row shading with business-driven color rules. This option allows turning striping off so only rule-based coloring is visible, ensuring clear visual meaning.
oh yes please.
I just made this idea visible for voting.