I initially thought the system wasn’t saving customers I’d entered but I realised it was just because I needed to start entering a search string for the results to start populating. Is there any way of having all customers listed in the search results when you open the Customer Search screen?
Purely because it feels like expected behaviour. If you’ve got a store with only 20-30 delivery customers it feels really odd to not have them listed when you open the page.
Also I’ve noticed if customers have an open ticket, they don’t appear in the search. Is that intentional?
If you only have 20 customers as kendash said you can change to an entity grid rather than search which is purposefully made for large lists.
As for open tickets, never noticed that but posibly, but may be the state filter for the entity screen.
The default should have search (to select incoming customers) and customer entity screen with grid for customers with open tickets…
It should not matter of the Customer has an Open Ticket or not. The Customer will show up in Search, unless you have a State Filter set.
P.S…
There is NO POINT in populating a Search Screen with all Entities. It is not designed to show all Entities; it is designed to show search Results, and that is why you must start a Search by typing something, even just a space or number is usually enough to begin the Search.
If you had 3000 Entities, and you listed them all by default in Search, it would take a long time to populate and you would think the program is frozen.
Anything less than about 50 Entities can easily use a Grid instead; that is what a Grid is for (Automatic View Mode), or a Custom Screen with an Entity Grid Widget. An Entity Grid Widget can be made to look like a list depending on column and row configuration.
BTW, speaking about trying to improve the usability of the customer search and such using the “lister”( I believe that is what it is called), adding shortcuts keystrokes seems more useful.
e.g. when I try to enter a ticket no. as the criteria, my hands are already on the keyboard, it seems faster to go back with the mouse to click the refresh and such.