Why I am abandoning Kinetic screens completely 😥

[hmwillett (Hannah Willett 🏳️‍🌈⚧)]

@Evan_Purdy

I’ve found its MUCH faster if you are operating directly in your web browser of choic

I’ll echo this. Once cached of course, it’s significantly faster.

[aball]

@klincecum , @Mark_Wonsil , the browser is definitely slower for us as well. If there are ways to speed it up, we’d love to hear. Smells like this thread wants to fork.

[jkane (John Kane)]

Ok, I’ve calmed down now.

@Mark_Wonsil

Our expectation was that not everything will work. It’s new. We decided to use Kinetic screens but if the functionality wasn’t up to classic or there were bugs, then we also have that classic screen on the menu. We have some users who still use the Kinetic screens while others use the same classic version. This gives everyone the experience of what is coming while still having stability.

I was taking close to the same approach, but we cannot even do that anymore because if you are adding attachments you now HAVE to be in Classic. This ends up being almost every function other than production workers.

@MikeGross

Have you gotten in touch with Tim Shoemaker?

I have not. I figured he would read this and if not, I just tagged him @timshuwy .

@jtownsend

Any step backwards from that simplicity is going to be rough.

And this is where I was trying to push through to users that things would get better and to just power through. But now I can’t even do that.

So, with less emotion, I was able to figure out that the production workers can still use the Kinetic UI for MES which means we can still move forward with tablets on the floor. But, everyone else will have to stay on Classic until the metadata gets fixed.

[MikeGross]

@jkane

production workers can still use the Kinetic UI for MES which means we can still move forward with tablets on the floor. But, everyone else will have to stay on Classic until the metadata gets fixed.

And after seeing all of this, ^-- this looks to be our implementation path as well for this year.

[klincecum (Kevin Lincecum)]

@jkane

I was able to figure out that the production workers can still use the Kinetic UI for MES which means we can still move forward with tablets on the floor

This is where I’d like to be, however, since we have needed customizations,
I can’t move forward with that.

I am not experience enough with the web ui to do what I need done.

I may have to pay @hmwillett to move down here. It’s ok, she can still keep her
job with @josecgomez .

[Mark_Wonsil]

@aball

the browser is definitely slower for us as well

So, the blanket statement of the browser is faster/slower certainly deserves some context: For example, from the Login screen: no contest. The browser goes to the Active Home page in under a second after entering credentials.

I am comparing running Kinetic in the browser vs running Kinetic in the .Net client - which is the slowest combination.

Where are you seeing slowness compared to the browser with those conditions? Where are you seeing slowness against classic screens? Are we talking number of clicks? Actual “spinning” time?

[josecgomez]

@klincecum

I may have to pay @hmwillett to move down here

[aball]

@Mark_Wonsil , dangit, you won’t just take my word for it?

(glumly heads off to substantiate statement with data…)

[Mark_Wonsil]

@aball

you won’t just take my word for it?

Don’t need data, just need the scenarios that are slower. Do they include customizations? Screen loading time? Downloads to Excel? …

[frontierits (Ed Stang)]

ARe all these issues noted persisting into the most recent release/update patch?

[klincecum (Kevin Lincecum)]

@Mark_Wonsil

Actual “spinning” time

This is what I’m referring to, at least I think so.

Performance in a screen once loaded, is most of the time faster for me in the classic client,
with classic screens.

I don’t use that embedded browser stuff, it’s trash.

[kylepbsps (Kyle P)]

Wake me up when Kinetic is finally ready.

[Banderson (Brandon Anderson)]

@kylepbsps waiting to be woken up… eventually…

[hmwillett (Hannah Willett 🏳️‍🌈⚧)]

I’ll be over here like:

[ridgea (Alex Ridge)]

[LarsonSolutions (Bruce Larson)]

Is there any place (maybe here) that Issues with Kinetic by module could be posted?

Following the standard menu

• Sales Orders
  Part on the Fly
  Can’t put in a revision on part on the fly

• Job Mgmt,

• etc…

• Purchasing

   Supplier Price List
   I just ran into an issue showing how slick Kinetic was when I tried creating Supplier partnumbers 
   by launching the process from the part.
   The screen starts out with a list of all suppliers, then when I added a supplier, I couldn't add 
   another supplier.
  

I don’t have time to enter a case or enhancement request to Epicor.
They need to make the process back the way they started, when you could flag the issue right from the user interface.

[Evan_Purdy]

@LarsonSolutions

when you could flag the issue right from the user interface.

They never explained why they got rid of that, did they?

[Randy (Randy Stulce)]

@Evan_Purdy

They never explained why they got rid of that, did they?

Epicor Ideas took over IIRC (Not to start a war or derail this thread) But that’s their preferred way for us to make suggestions for improvements. Bugs go to Support.

[LarsonSolutions (Bruce Larson)]

@Evan_Purdy

They never explained why they got rid of that, did they?

I think when they release 2021.1 they thought they were done with the “Beta” phase of the project.
I know some of the issues I brought up were pushed back telling me that I should submit a case.

Crowd sourcing for ERP development should have some boundaries.

Anyone know how to create a Wikipedia
“EpiUser Kinetic”
User’s guide to soft spots in the new UI.

[josecgomez]

@LarsonSolutions

I don’t have time to enter a case or enhancement request to Epicor.