Hi everyone ![]()
I’ve just published a new short video that solves a small but slightly annoying UX issue I’ve bumped into many times with Knack search views.
Out of the box, search components don’t always behave how users expect when a page first loads — especially when you’ve set “Show results on load” and also applied default search values. Even with a default like Status = Active ticked, users still have to click Search before the filter actually applies, which can feel confusing.
In the video, I walk through a simple real-world example and show how a tiny JavaScript snippet that automatically trigger the search when the page renders. From the user’s point of view, the page just loads already filtered, no extra clicks, no head-scratching.
I’m not a developer, so this is very much a practical “builder-level” tweak rather than anything clever. You just drop the snippet in, change the scene ID and view ID, and you’re done. I’ve linked to the code on my website.
If you care about making search views feel more intuitive for clients, this might be useful. It’s been a while since I last shared a video, so any feedback or encouragement is always appreciated!
Cheers - Carl ![]()