The workaround is brilliant but not realistic for many cloud customers to deploy. Any word from Epicor on delaying the release of this version until the bug can be fixed? Or skipping .9 entirely?
(Just because there’s never a bad time for a Caddyshack ref)
EDIT - EpicCare case updated…nothing about a delayed release, but they’re requesting a hotfix to port back the solution to 2026.100.9
Just checked after the Pilot upgrade this evening and the issue is not resolved, any word on a hotfix?
PRB0321431 - still at “submitted to development”
Come on Epicor
Same here. Checked Data Dictionary Viewer and see the same problem.
Didn’t get an all-clear for the .9 Pilot install…for all we know they could be dropping fixes as we speak!
…maybe…hopefully…
All clear and still broken. I have a PRB
CS0005583366 / PRB0320771
So Support’s position is nothing can or will be done about this. Our environments will be updated on Monday, breaking over 100 grids, and they will not lift a finger to intervene, nor try to express any kind of urgency to development. When I expressed my dismay, their advice was to talk to the cloud team if I didn’t like it. When I questioned how that could be done, since of course we have no way to contact the cloud team outside of a support ticket, they changed their answer to call your CAM.
I can only guess that most on cadence cloud customers have not tested in Pilot and not ran into this issue yet or the noise would be a lot louder on this issue. Come Monday its not going to be pretty as Epicor continues to push breaking changes on top of breaking changes.
Complete indifference…what’s worse is that we won’t know how deep it goes in .9 with the limited time provided for Pilot testing. I just opened up SOEntry and the basic filtering seems to be OK…but how many screens are going to crack?
Support won’t refer it to dev, won’t refer you to the cloud team, says contact your CAM. I’ve been waiting 10 days for an inquiry on Prism from our CAM. If the CAM is that slow on the draw for a possible sale, imagine the lack of alacrity you’ll get on this.
Frustrating and demoralizing.
I won’t even bother, even if they do respond, they have no ability to to do anything. This is a product development issue. Btw Gabe did post a list above, its over 100 screens that are affected.
Filters are also broken in Material Queue Manager. The reason I know this is because 100.9 fixes a different issue that exists in 100.7.
Grouping by a column in that grid changes the queue entries that are in the grid. Filter by STK-SHP (Stock to Shipment). Turn on grouping, and group by the ‘Selected By’ column. The entries in the grid change to STK-INS (Stock to Inspection) entries.
This is fixed in 100.9 but now some of the filters on that same grid are missing. R O F L.
Yuck…didn’t realize the depth of this debacle. Oh happy day.
one line of javascript yet powerless to turn the ship in the face of sudden catastrophe. Sad.
We need client-side extensibility support like a while ago.
Really sucks when you can see the train wreck coming but are powerless to inform the powers-that-be in time to stop it.
First CI/CD release (2026.103) is publicly applied on October 6. to pilot environments.
I think it’s available to be downloaded on 08/11 though based on past things we’ve seen.
At that time things like this should stop happening, I hope.
Thank you @GabeFranco and @aosemwengie1 and @Schae235 for reporting this for the upcoming patch. I’m sure I’ll hear it from people. We can’t even commit to testing patches because of the cadence so this surely will be a surprise to people.
I have submitted Case # CS0005594139 that is also associated with my Problem # PRB0317436. I also have the Filter icons missing on my screens that you all have mentioned and my MES Work Queue (which is the topic for the Problem # I mentioned) is more screwed up than it was after the last upgrade. Now when you are on the active tab is MES and click on a job to End Activity it brings over all the Current Tab jobs into the Active Tab screen. Not good!!! I have submitted a video to Tech support regarding the MES work Queue. Craziness!!!
I am now hearing that there WILL be a hotfix. Do not have any additional details yet.