I am glad that there will be a hotfix but these dot upgrades aren’t supposed to break anything and they essentially gave us 3 days to test it (In non-prod on Wednesday and Live on Sunday)?
It would be nice to have more than 3 days, and as much or more time to review hotfixes as well.
As far as I understand it, when CI/CD starts, that’s when, they have committed to not breaking anything.
When the “new” product lifecycle was announced 10+years ago, it was promised that dot releases would be non-breaking. Every release since then, it has been re-promised that THIS TIME we have learned and NOW there will not be any breaking changes in dot releases. This cycle has repeated so many times its barely worth commenting anymore, because everyone knows that Epicor will absolutely introduce breaking changes in any and every type of release, always. You can easily find dozens of threads where this exact pattern is repeated on this very forum. So forgive me if I have 0 confidence that “this time” will finally be different.
Oh I remember… They been saying that forever, “no need to test”. Famous last words before an analyst or admin got fired or a mark on their record for not testing and getting hosed.
PRB0320698 seems to be the main problem and it does look to be targeted for .9
Thanks Jonathan.
Targeted for .9…this weekend for go-live? Or am I pushing my luck? 
I read something about a hotfix, truth is I’m not sure so don’t quote me on that, better to ask support directly on your respective cases. Just wanted to provide the PRB reference to make it easier.
Understood - not trying to put you on the spot - thx
Support is now saying a hotfix cannot be requested without business justification of the impact of the issue.
Software that used to work no longer works…and we’re supposed to justify fixing it.
That pretty much sums up the week.
What I love about these recent updates is the vast majority of people in my workplace - especially our makers - think I am the one who is pushing them out and breaking all of their dashboards and processes, so the general consensus of late is my department is inept (which to be honest they are not far off) until we can get them a workaround to a problem Epicor created. And then they break it again. (Grids haven’t worked consistently between any update since we went live with 2023.1).
Looking forward to the Monday-morning inbox meltdown 
I mean, why worry about it. You can just post technology jokes right? It’s not like this stuff is important or anything.
Ours too and they think we can control WHEN the update occur which we can’t being SaaS we’re stuck on someone else’s schedule.
So I see now Live is hotfixed to a version that was never released or tested in Pilot. Have only done a little testing but the grid filters and sorting functionality appear to be restored with this hotfix. But Pilot is still broken. I am baffled why code would be pushed straight to production with no testing window at all.
Grid filters are partially broken on my LIVE:
I have to click the down-arrow “preload” icon for the filters to show up in those columns. Did not have that issue in the prior version.
Also, a little PSA:
Until I cleared the cache (“Reset application back to defaults” on the login screen), my version number was reporting incorrectly:
And clearing the cache and logging in again:
