Juan Carlos Pérez
19-Aug-2026 06:09:02
*Popup LOV search in 26.1 — did we lose wildcard % for good?*
Hi all :wave: Hoping someone can tell me I'm missing an option, because right now this feels like a real step backwards.
Up to 24.1, users could type % in a Popup LOV search and it worked as a genuine LIKE wildcard. Ours use it deliberately (not randomly) to match several substrings within one entry, e.g. A%B%C to find rows containing A, then B, then C. Fast, powerful, and completely muscle-memory for them.
In 26.1 the unified LOV search escapes %/_ as literals. I get the consistency goal with Select One/Many and Combobox, and Match Type / Case Sensitive are nice. But Match Type = Contains only does a single contiguous substring match, so the multi-token search is just… gone. No replacement, no compatibility toggle, and no bind for the search term either. Compatibility Mode set to 24.1 doesn't bring it back.
So the removed capability wasn't swapped for something better — it was removed outright, and now recovering it means per-item plugins + hand-written predicates. In our case that's hundreds of SQL LOVs, which is not realistic.
My question: *is there any reasonable, supported way to get wildcard/multi-token LOV search back that doesn't rely on third-party plugins?* Anything declarative, a documented bind for the search term, a setting I've overlooked?
To me the obvious fix would be to extend the existing *Tokenize Row Search* parameter (which already exists for IR/IG) to the LOV item types — same behaviour, consistent with where APEX is heading. I've added this to FR-3800 in the Ideas App, but I'd love to know if there's something usable _today_.
Thanks :pray: