Opppps; Browser only shows hot keys as a menu item, my bad.
1 Like
Truer words were never spoken.
Any desktop software product is going to be keyboard- (or keyboard-and-mouse-) biased. The Windows CE-based Epicor Handheld modules were designed for the scanner devices they were used on… but even the current (browser based) Mobile products really require a keyboard. An “intelligent” barcode interface is going to need a wholesale rethink not only of screens but for many of us also process flow.
3 Likes
You reminded me of an old Fridea!
Could be worse, some of us otherwise smug Linux users gloating about not having to open Windows to browser client can’t open hotkeys editing. Control-alt-h is often intercepted to launch the clipboard manager in various Linuxes.
3 Likes
@timshuwy
In Kinetic revision 20232Predictive search was based upon contains and it worked very well. When 2024.1 was released predictive search was changed to starting with. The reason given was the field name was starts with. Development wanted Kinetic to work like Classic.
This was a major change that affected a few of my customers. Epicor didn’t even acknowledge that it was a step backwards.
When a customer was searching for a part to put into the material, they don’t know what the description starts with, they know that “red” is the color of the material and that string of characters is contained in description.
I posted the disappointment on Epiuser because in spite on escalation of the case, no one could explain why they were taking away a capability in Kinetic to give it parity to classic.
This was the final straw among many that it was time for me to move on.
This demonstrated that it was not worth bringing up issues.
6 Likes
@LarsonSolutions if you have a case number, I would like to have @bconner take a look at it. I am personally not aware of which decision made this change. We are not intentionally trying to degrade the browser experience to make it in parity with the smart client.. if anything it is reverse of this. There are many feature that are only available in the browser.
2 Likes
Depending on your use case could could use a custom field for the scan.
As an example, I created a custom text field on the start activity mes screen where the barcode scan is dropped. Then I set an on-blur trigger for that field that punts it over to a function that parses it and assigns the values to the right fields on the entry screen. Then you aren’t relying on the correct tab order, the rate at which the barcode scanner feeds vs kinetic updates, etc.
3 Likes
Payroll check entry in classic, the actions drop down menu listed steps for "Calculate Overtime, Calculate Tax’s and Deductions, Printing Check Register.
Kinetic interface they are now nowhere to be found, searched help, etc… nothing.
Did find a knowledge article on processing payroll checks where technical support typed up the steps. So now if you pick the first detail record which is the first check generated. On this record you will find on its overflow menu the steps missing. Since you are on a detail record now your first intuition would be do I have to do all these steps for each check? This is not overtly obvious or intuitive at all. After you run the steps and look at other records you see it did indeed run for the entire batch. Can this at least be added to the help?
1 Like
@timshuwy
There’s an idea KIN-I-5267 posted too
Case CS0004446599
The last response from EpicCare
2024-07-25 13:15:44 -Daniel DiEsposti
Hi Bruce,
Development reviewed PRB0285319, and Rejected the Problem Case, for the following Reason:
We have updated the functionality to align with the classic application as part of this ticket: Jira. As it is working as expected, we are rejecting this issue.
In other words, the Bug was with how the Kinetic Predictive Search functioned in Kinetic 2023.2 (as “Contains”), and the Fix was made to Kinetic 2024.1 - to make the Kinetic Predictive Search function like Classic Predictive Search (as “Starts With”).
I will put this Support Case into a Suggested Resolution State, in case you have any follow-up questions.
Daniel DiEsposti
2024-07-21 12:37:51 -Daniel DiEsposti
Hi Bruce,
I decided to submit the reported issue directly to Development, via a Development Problem Case, asking them to review and provide feedback.
The Problem Case Number is PRB0285319, and has the following Description:
Problem Description: In Kinetic 2023.2, when a value is added to a Kinetic Field, one that is tied to a Kinetic Predictive Search, the Kinetic Predictive Search runs and returns all records that “Contains” the value added into the Kinetic Field. However, in Kinetic 2024.1, when a value is added to a Kinetic Field, one that is tied to a Kinetic Predictive Search, the Kinetic Predictive Search runs and returns all records that “Starts With” the value added into the Kinetic Field.
Expected Behavior: I will leave it up to Development to determine the correct Behavior.
I will keep this Support Case in my queue until Development finishes reviewing the Software Problem I submitted to them.
Please note the next time I will update this Support Case will be when Development does provide me with their Feedback.
Please let me know if you have any questions.
Daniel DiEsposti
3 Likes
Thank you. I have forwarded on your comments. the Idea was also helpful, and should help the case move along.
1 Like
Following on after Tim, David and I discussed - We’ll look to bring this back as some kind of option wrt what kind of matching to use in predictive.
Development wanted Kinetic to work like Classic.
This was a major change that affected a few of my customers. Epicor didn’t even acknowledge that it was a step backwards.
I think in this case we can say it was a step sideways :). For you it is degraded, for the customers who reported it as a bug that it didn’t work as they expected from classic (startswith) we made an error rebuilding the feature from classic (which is true, it was intended to mimic the behavior.
So, we think both ways have value and will be looking to have some kind of preference or per search setting around it so you can do either or.
11 Likes
Bank Statement processing not technically a parity issue because it is possible to use the Kinetic screen but it’s a frustrating experience compared to classic. We are 99% Kinetic screens here and very happy with them but revert to classic for bank statements every time.
It’s improved since they first released it but is still not where it needs to be the issue in the workbench occurs when you have a large number of suggested or partially matched lines the filter for the transactions in the work bench is matched or unmatched you are sol if it is a partial or suggested.
The best way we have found to deal with statement lines that have a suggested match is to revert the status to unmatched and then process it. This is a pita we end up with a lot of suggested matches when we have credit card lines of the same dollar value.
Then there is the quick matching section which is a breeze in classic but also fails to handle suggested matches in kinetic.