Cross company linking broken in kinetic?

I’ve started trying to deploy some of our dashboards as kinetic apps to make them available in the browser. When I use the kinetic version of my dashboard, when I right click >open with on a record in one of the other companies, it no longer launches the screen in the right company context to load the record. Instead it launches the screen in the CURRENT company context and then asks if I want to add a new record.

Is there some step beyond deploy kinetic app that I am missing? Is this really broken in kinetic or am I missing something obvious?

I went to support but as usual their answers are a)working as designed, if you want it enhanced enter an epicor idea and b)contract with professional services. You may guess how I feel about these answers.

I think you need to use multiple accounts so you can hide your identity better.

You’re on a list.

1 Like

Don’t know whether to laugh or cry at this. Anybody want to enter a support case on my behalf and try to get a better answer?

Season 6 Episode 3 GIF by Parks and Recreation

Before anyone suggests escalating the case . . .

Reject and explain again. They obviously don’t understand.

I mean, I gave them the dashboard, a screen recording showing it working in classic and not working in Kinetic, and the same explanation I posted above worded 5 different ways. Not sure what more I can possibly say.

I’ve got some suggestions, but if you weren’t already on a list like we laughed about, you sure
will be after you repeat them.

1 Like

Agreed - reject and escalate to see if you can get a ruling from Dev. This sounds more like they broke something and it needs to get turned into a ‘problem’ to be fixed in an upcoming patch. If the escalate doesn’t work, reach out directly to the Support group manager(s) via email. They are pretty good about taking up a clear case of “WTF happened to this functionality” :slight_smile:

So the screenshot above IS the response to my escalation from the support group manager. Feel free to suggest a specific person I should reach out to . . .

There wasn’t a name on it, so I assumed it was from the support analyst on the case. Let me dig around and I’ll message you directly. Give me a little bit - my day is a bit hectic.

I whited out the screenshot to protect the guilty.

But I was starting my own list!

@aosemwengie1 - I’ve been doing some testing in case I need to open a ticket as well, and it seems to be broken for me as well in 2023.1. Does this scenario agree with your ticket? And can you share the Case #?

I’ve got a simple cross-company/all companies “Customer” BAQ we use to monitor duplicates across multiple companies. It’s on a dashboard that opens in Classic UI, and I’m using the right-click open-with function on the Customer ID field.

In 2021.1.x, I can get Customer Entry and Customer tracker to open properly in the company context (the global options are on so the status bar shows the details).

In my newly installed 2023.1.4 version, it works equally but not without errors because my Customer screens are customized and I have not fixed them yet - but Create Case & Create RMA work fine and display in the company context.

After I’ve deployed this DB as a Kinetic DB App and created a menu item for it, every right-click open-with from that Kinetic Dashboard fails to open the record in the correct company context and often fails with ‘invalid record’ errors.

2 Likes

Yes precisely the same scenario.

Cross company dashboards are literally the only thing that make Epicor usable for us since the entire rest of the application ignores the fact that people need to work across companies. Not having the open with functionality is a deal breaker in moving to kinetic - we have dozens of these dashboards. It’s really frustrating that Epicor support refuses to acknowledge or even try to understand the issue in light of their stance that we all need to move to kinetic ASAP. Maybe if you open your own case you will get better traction than I did.

Get you CAM involved.

1 Like

We are in the same boat - all mine are cross-company as well.
Forcing this issue will serve us both, and everyone else.

3 Likes

Enter the issue into IDEAS anyway, as they asked. Make it clear that it was working fine in 2022.2, and 2023.1 broke it, and you want to get your functionality back. The more pressure from different directions, the faster it’ll get resolved. Maybe we’ll get lucky and @timshuwy will reject the Ideas back to dev as a PRB!

1 Like

@timshuwy said at Insights this year, “If it works in Classic and doesn’t in Kinetic UI” we’re to let them know. So this is a perfect case especially since it broke from 2022.x to 2023.1.

4 Likes