We have a custom Kinetic Layer on Office MES Start Rework Activity that has worked fine for years. This weekend we upgraded to 2025.1.11 and now the customization displays in Web Browser but does not if using Smart Client. Has anyone seen this before?
I know the push is to use the browser but many of our users are not there yet.
Yes, I have logged multiple support cases begging for this to be fixed. Support is dragging their feet to even submit it for no reason I can begin to comprehend. I can’t believe this isn’t a huge priority to fix, pretty much every customization we have has slideouts that no longer work in the client because it only loads base with no layer.
Ugh - have you done any workaround other than to use Browser? We also had this customization in Classic and it still works there. I did test unchecking the Slide Out on the Parameter in the layer and it opened a separate menu in Classic format in the Smart Client but then broke the Browser…so that isn’t an options.
I haven’t found a workaround other than having people use the browser.
Create a menu item (or under Process probably for this) and set the layer, then app-open reference the menu ID and remove the layer
Does that work for you? I just tested it on one of mine and now it loads the custom layer in the client but not in the browser.
But! If I put the custom layer on the program on the menu and also reference the custom layer in the app open widget with the menu item that seems to work.
I was just finishing testing it and mine is working now in both the smart client and browser. I used the existing process PR000082 and added my Kinetic Layer under the Kinetic Customization. Initially I only updated the menu to include the layer and left my app-open widget with the layer and that worked for me also. But removing the layer from the app-open also seems to work for me.
If I don’t reference the layer it works in the client but not the browser for some reason. I swear I tried this exact thing a couple of weeks ago and it gave me an error.
It seemed to work for both when I did it this way
Thanks this is awesome!
Interesting… I just did my changes in our Prod environment and there I had to leave the layer on the app-open or the browser did not open the custom layer. In Pilot it worked without the layer.
Its definitely inconsistent.
@tkoch THANK YOU for this suggestion! 
it continues to work and Epicor doesn’t break it in the next upgrade
You should mark his post as the solution so its easy for other people to find it 
Well just tried the exact same thing on another one and it didn’t work, so I guess its hit or miss. Sigh.
I am running into an issue where our custom layer displays for some users and not others from the smart client…very strange and still trying to figure out why.
Update: I ended up opening a case with support (CS0005077823) and recently received the following update:
This Case was transferred to the ICE Tools Support Team, as an Application Studio Issue, asking us to review.
What is being reported appears to be related to a know issue. The Development Problem Case Number is PRB0303297, and has the following Description:
Problem Description: After Upgrading to Kinetic 2025.1, in Application Studio, setting up app-open with View set to a Kinetic App/Program, and with Layer containing a Kinetic Customization Name, the following issues are reported:
On a “Cloud” System, the Kinetic Customization displays in a Browser, but not using the Smart Client software. However, this occurs only if the app-open Slide Out property IS checked.
On an “On Premises” system, the Kinetic Customization displays in a Browser, but not using the Smart Client software. And this Smart Client Issue occurs when the app-open Slide Out property is either Checked or Unchecked.
Expected Behavior: The Kinetic Layer should always display in the Smart Client Software.
An a Kinetic Update Request for both Kinetic 2025.1 and Kinetic 2025.2 have already been submitted.
And last week, Development informed me the are already testing an Internal Jira Story (KNTC-26858), which should resolve Multiple Update Requests. And once their Testing is competed, they should be able to put a Target Kinetic Fix Release for Development Problem Case PRB0303297