I am on my 3rd issue since we upgraded to 2025.2.10 over the weekend – so just 4 workdays into this release. In each case it requires a customization to an app-open changing the View to Menu ID.
- Launching Corrective Action from DMR Processing was throwing the error shown in this post. We didn’t have a custom layer on DMR processing but did on Corrective Action. If I removed the custom layer from Correction Action it worked as expected but we need this custom layer. Used this to resolve Corrective Action from DMR - #14 by leonardpothier
- PO Link from New PO Suggestions > Generated POs – this didn’t throw an error but it took the user back to the New PO Suggestions Main Grid instead of opening PO Entry. Same basic issue, we have a custom layer on PO Entry but not on New PO Suggestions. I have a case (CS0005342878) open on this as it was my first and I hadn’t found this post yet.
- Engineering Workbench button from Part Maintenance – this didn’t throw an error but it took the user to Method Tracker instead of Engineering Workbench. Here we have a custom layer on both Part and Engineering Workbench but if I remove the layer from Engineering Workbench it resolves the issue.
I have also tried copying the base layer and using it as the Kinetic Customization on the menu – issue still presented. So basically, you can’t have any Kinetic Customization on a menu and have the link/button/action from one menu to another work as it did prior to this upgrade…if the app-open has the application name in the view. This sounds like a 
to me!
So, rather than fix what they broke they are going to make multiple customers create multiple customizations to correct their issue. These workarounds are not simple – they require figuring out the correct events/controls, copying and creating custom replacements as you can’t update the vanilla events/controls…which BTW would make things so much simpler.