Epicor has taken a big step backwards with changing the predictive search. They don’t see the value in having the ability to search for “Contains”.
The use case is when building a BOM, you can stay in the grid view of the material table and just type in a few letters that are contained in the description of a part and select it, faster than searching in the “engineering” view of the part table.
Epicor has been able to replicate the issue – but currently they are not calling it a flaw. From EpicCare Support.
I ran a test, side-by-side, in Kinetic 2023.2.22 and Kinetic 2024.1.8 And after a few tests, I do see what you are reporting.
In Kinetic 2023.2.22, when I key in an A in the Customer Field, all Customer Records whose Name “Contains” an A were returned, which does not look correct, as the field states “Starts With”.
In Kinetic 2024.1.8, when I key in a A in Customer, all Customer Records whose Names “Starts with” an A were returned, which does look correct. *
Since it appears Kinetic 2024.1.8 is correctly returning the Records, I will post this issue on our Development Yammer Site, and let you know what Development States. Maybe they can provide the Problem Case that made this change.
Let’s keep that Classic capability as we all know - Classic is better than Kinetic.
From EpicCare:
#########
"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: https://epicor.atlassian.net/browse/ERPS-238143.
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."
##########
fixed 
