Has anyone else experienced issues with moving Kinetic custom layers between environments with 2025.2 Cloud environments? I’m seeing a number of issues with Kinetic layers lately which is making me wonder whether I have lost the plot, or there is an actual problem.
Deploying a workbench solution to an environment, targeting all companies
if the kinetic layer doesn’t exist in the new environment, solution workbench says it succeeded, but the layer does not appear in App Studio, nor does the menu item load it when running the program
If the layer already existed (and you’re updating it), the install fails
installing a solution to target a specific company - solution workbench says it succeeds, but does nothing (doesn’t override previous layer).
Updating and re-publishing a Kinetic Layer (built for all companies) only applies the changes to the company you made the changes in. Seriously? Have we got to repeat our changes for every company now?
I’ve got a couple of cases in with Epicor Support at the moment, but considering 2026 is only a few months away, I thought I’d ask if anyone else has come across it or knows of any workarounds
It seems to be ignoring the ‘All Companies’ and setting it to the current context company. You then check other companies and they don’t even see the layer.
It’s a pain in the rear! We are hoping that Epicor fixes it soon.
I had a ticket with support recently (unrelated to Solution Workbench) where I was told that it is a known issue that SW currently is ignoring the All Companies check box. My issue was around layers as well but exporting the layers from Application Studio, importing them with All Companies does work.
I’ve not seen the issue where publishing only pushes to the current company though, I’ve seen Menu Maintenance not always honor the All Companies flag for menu items but that was specific to how they changed how you call the menus from their application name to the menu id directly.
I found when exporting layers from App Studio I’m always met with the same error. The layer already exists in another company.. Yeah T_TenantID aka ‘All Companies’ even thought all companies are ticked in the import slideout for App Studio.
The only current work around is to edit the base layer if it’s an old Dashboard conversion or the ones I have created manually (we do this more often now)
Then export the whole app using solution workbench and import it..
We’ve also been finding recently changes aren’t saving correctly.. If I wrote an expression e.g
ALL: If you experience this, please submit a case with support. While this forum is a good place to discuss problems, and find out if someone else experience it… the only way to actually get the fixes reported to the dev team and to get it fixed is to get a case submitted. Then it will be validated, get a PRB assigned, and Dev can then fix.
Yes, I already have a case in with Epicor Support which has been converted to a problem ticket.
With Epicor 2026 fast approaching though, and going browser only, I thought I’d reach out to see if anyone else had experienced similar issues and had come up with a clever work-around that could be used in the meantime.
This is an issue (in different forms) that we have had cases raised for since the beginning of 2025.2…
The workaround that I devised for our technical team is to create a new Solution Workbench Element that replicates the functionality of moving Kinetic layers in solution workbench from 2025.1.
In 2025.2 they changed the Solution Workbench to use the same functionality that Application Studio Import / Export uses which is why they both have the same issue.
This workaround puts it back to 2025.1’s way of moving the raw record in XXXDEF. This is only needed on systems you are creating solutions from.
Open Solution Element Entry (note, only available in classic. Support case raised)
Create a new Element as per the below. You can add more Display columns if desired.
Key1 is the Layer Name and Key 2 is the Application Name
Then choose this new Element when creating your Solution. Import as usual.
Note. This reverts back to 2025.1 logic which requires you to refresh the cache on exisitng layers, open the screen and do Ctrl + Alt + I or open the layer in Application Studio, wait for it to load and then it will be refreshed and available as usual.
