Cloud continues to be a disaster, even as we now see a new fun 2026.1 classic deprecation warning snooze in Kinetic UI 2025.2.5. The workarounds have workarounds that have workarounds… with a foundational piece of the software: App Studio.
App Studio: You cannot import layers as all companies - in 2025.2.3, this was completely broken and provided an error. Fixed in 2025.2.4, but now it just says successful - no layer is actually imported. Workaround? Import as company specific.
App Studio: You cannot use company specific layers properly, they will eventually refuse to commit/publish. PRB exists, workaround is to save as all companies layer.
Solution Workbench: Just use Solution Workbench, you say? Layers greater than 50 characters will refuse to import - PRB is slated for 2026.1!!!
So, the workaround for solution workbench is to import/export via App Studio, which itself requires you to override back to company specific, which you then must save AGAIN as all companies.
EPICOR PLEASE TEST YOUR SOFTWARE!
Edit Footnote: I’ll add that these are pilot environments, but it is making cloud migration a huge hassle with certain processes. It does not give me the good feeling it will be ready prior to everyone’s upgrade to 2025.2 in two weeks.
That really goes to any company that sells software. QA seems to go in cycles where there is fewer obvious released bugs then cycles down to where there are many released. We’re at a low point of QA it feels to me and I too hope for it to cycle back up to high quality before Classic sunset.
After a response from support, I am pretty sure Solution Workbench is fully broken. I tried building a solution and I get Error Package creation failed: startIndex cannot be larger than length of string. (Parameter ‘startIndex’).
Support’s response was;
In 2025.2.4, Epicor uses a new internal parser for solution XML metadata. A Substring() call in the SolutionBuilder class incorrectly assumes certain strings (like VersionInfo) are always a minimum length. When any field is shorter or missing, it throws
This is tracked under internal defect CSF-19548 / PRB0247998, expected to be patched in 2025.2.6
I went as far as just adding an out of the box BAQ and it still fails. Of course 2025.2.5 was released yesterday, so my upgrade may have to wait a bit because I’m not doing it without the ability to export customizations my consultant fixed in the Test environment.
PLEASE