When upgrading to 2022.2, custom kinetic layers are removed from the menu.
I originally reported this on February 6th. That case bounced around several teams was so thoroughly garbled that they had to close the case and start over again. They then opened a separate case for the issue on February 16th. On February 27th they successfully reproduced the issue with a copy of my database, however to date, they have still not submitted the issue to development. The response to my escalation was, we don’t have approval to submit this to development, just use solution workbench to fix it.
I imagine other people have reported this too? Anybody successfully gotten support to submit this to development and/or received a PRB for it? I am baffled at the handling of my case.
When I worked for an Epicor partner, the support experience was awesome from Epicor. Now that I work as a customer, I’ve had nothing but “worst experiences”. It’s a battle to get any useful outcome.
Contacting your CAM is always an option. Maybe @timshuwy can help shed some light on why they may be prevented from submitting to development at this time.
edit: I might add, they won’t fix this anytime soon. A workaround is usually going to be your best bet white it sits in dev (if it makes it there)
Most of the people I know, dont use Kinetic UI yet or layers… They dabble in it, they look like they use it on the forums… But when you ask, they’re like “Nah, we stay on classic until 2025 atleast”.
In other words, I have no confidence of people reporting this. Which is too bad, because we assume Kinetic will be bug free in 2025, but if we don’t report it… Might as well start using it today.
Exactly, this is why I report every issue even though its a massive pain and battle, but recently it seems like the process has broken down even more than usual. There are multiple issues where it was working in 2021 and now broken in 2022, so they can’t even blame it on the kinetic transition. Its just poor QA.
The menus though are tough. As I am sure you have seen it has changed a ton.
First there was application maintenance or something like that. Then they merged that with menu maintenance to some degree.
And then you had to make sure to set up menus a specific way for them to come over correctly BUT there were a couple different ways to make something kintiec and use a kinetic customization layer.
In short, it’s been something they have continued to change and can’t quite seem to get right for those who are upgrading. I think the menu works fine for the most part, but upgrading has been a struggle.
They told me to make a copy for the system menu and change the copy to kinetic app.
When you make a copy of the system menu, the copy replaces all instances of the system menu for the given company you created the copy for- until you delete the copy menu, then it goes back to the system menu…
I told them that is patently absurd given how many times things like order entry/order tracker and customer/customer tracker appear in the menu. And yes they gave me a datafix for it.
Ah. I must have missed that part of it, you would have to do it for each menu…
I guess I thought you copy customer tracker once and then it would apply to all, but I can see why you would and wouldn’t want that. So they probably just copy it for one instance
Exactly - you would have to copy every single instance individually for every company (we have multiple) and assign the customization to every one of them. Instead of simply to the already-existing menu items which is enough work in and of itself. There is a kinetic idea out there that would make the datafix functionality part of the product but very few votes on it unfortunately.
Yet another example of the fail that’s the current voting system.