Autocomplete causes DB query for every keystroke - how to prevent this?
Pega 8.4.1
I have an autocomplete whose "list source" is a Data Page. This Data Page has a Report Definition as its Data Source.
In the autocomplete field, I type A. Using tracer I see that a list came back from the DB containing 256 entries.
I continue typing, adding the next character M. I expected that Pega would be smart enough to filter the existing 256 entries to produce a smaller result set.
Instead, I see a DB query (from the underlying Report Definition).
Is there a way to configure this so that the second character does NOT query the database?
Updated: 3 Dec 2020 20:55 EST
Pegasystems Inc.
JP
Supposing that you type "A" and then select it and paste "BCD" from the clipboard to replace it, in this case it would be wrong to try to filter within the previous A list. Also, what happens if the user submits a new A entry from a separate client - it will never show up if you do not requery the database.
The Pega server actually doesn't know what the user is doing in the browser until the form is committed. The browser only knows to make a new list request upon each keyboard event. There is a limit to how much logic you can ask the browser to host.
Pega offers the Minimum typed characters option for you to reduce the database overheads involved.