I opened our customization menus in the web version. Most of the menus opened well. But, only a few certain menus did not open. So I looked at the menus that wouldn’t open and noticed a difference between them and the ones that did.
Most menus have the “From To Use” field set to “User Choice”, but the menus that don’t open have the field set to “Kinetic”. But, when I created all these custom menus, I created them in the same way.(BAQ → Dashboard → Menu Creation). And this “From To Use” field was not an option I could select.
Why did this difference appear? And is this the reason these menus couldn’t be accessed in the web version?
Thanks in advance!
If it’s a supported app, you may need to pop into Menu Maintenance and configure it to open as Kinetic. In Kinetic Menu Maintenance, check the “Kinetic” checkbox. Then click the search on “Kinetic Application” and select the relevant app. If it populates a URL value, you’re on the right track.
Even if it’s a custom dashboard, it’ll look something very much like this. Same for SSRS reports, and those sometimes need another step but it’s been a while and I can’t recall that precisely off the top of my head. Something like Report Style → one of the window menus (‘tools’ I think?) and something like “generate form”.
If the browser client is nigh for you as well, it’s worth the time to audit all menus. Get a complete list, filter where “URL” is blank, and investigate those. I had to fix a lot of stock menus.
As you can see in the screenshot above, the menus marked “User Choice” and without URLs, like the one in the right screenshot, appear correctly. However, the menu marked “Kinetic” does not appear. That confuses me even more.
we have had reports of menus not updating correctly, and have a special project to address this specifically for 2026.1. The challenge is that menu seed data is managed by Epicor, but you also can make your own changes. We typically do not touch custom menus.
in at least one case we studied, we found that the user was complaining that we didn’t fix a menu, but it was a custom menu… that said, we also realize that with 2026.1, we need to somehow alert you if we find a menu that is now a dead end. Just today, I saw a report coming from a developer who has put together a list of many scenarios that we need to catch.
BUT there has also been multiple people report that certain programs such as “Time and Expense Entry” do not have a kinetic version. This is an intentional fact. We actually split Time entry from Expense entry. If you look on your menu, you will see that there are these two apps AND the Time & Expense entry. The old combined program will go away with Kinetic 2026.1 as we do not plan to replace it.
Any chance of those changes being added to a later version of 25.2? If it’s not fixed until 26.1 we just have to trust that it’s “fixed” without the ability to test. And there’s no fallback to classic in 26.1. If a menu isn’t wired up correctly you just wouldn’t be able to open the app.
I understand the challenge there. The community gets upset when you do touch custom code. And upset when you don’t and it leads to something not working.
And hence why timely and detailed release notes with breaking changes highlighted, communicated to customers in a timely fashion is just a little bit important
Now, if you still want the classic dashboard launched from the web, you still need the classic client (until 2026.1 takes it away) and then the Edge agent will open it… but I always thought that was… an odd strategy.
This is a bit of a different question, but after the Smart Client is shut down in May, will this way of opening the classic dashboard from the Edge agent on the web also be shut down?
