Our Pilot and Third environments are in the Kinetic version 2026.100.3 and the problem is still there. In our production environment we are still in the 2025.2.16 and there we have no problem.
Yes, the hotfix has not been applied yet.
I see that you work at Scherpthe, we are a customer from Scherpthe. Can you keep me updated when hotfix will be applied. I also made a case with Epicor, hopefully this speeds things up.
I look forward to jumping to 2026.100.* with a certain degree of trepidation but I am sure we will all survive with workarounds and moaning, just like we usually do.
Incidentally, with regards disk (yeah, I remember the IBM AT and XT’s with 10MB HDD’s) at college we had Apricot accounts computers that had no HDD just 2 floppy drives, one for program and one for data.
- thems were the dayz!
Its incredibly simple if you have any experience with API’s. Ive completely abandoned the DMT tool because its so terribly slow and has inaccuracies for what tables required columns are.
Doing an update of 3000 parts will take an hour or two to run with the DMT tool. If I do the same update using the API’s it takes 50 seconds. No clue what Epicor is doing behind the scenes with their stuff, but the API isnt why everything so so freaking slow.
I normally write Python scripts if Im just doing it, but if users are doing it I usually make a web page for them thats hosted internally.
All I can is yes and thanks for sharing and not accepting mediocrity, we all need to question what is going on… clearly there has been liitle improvement in years) full disclosure post Epi users meetup post.
And… ?
We’ll all be beta testers come Monday…good luck to all.
This appears to be working for On-Prem. Just tested 2026.1.5
Maybe it was a dud install