I want to share a recent experience that inspired me and led to the video below. Earlier this week, during a session with one of my long-time clients who has been using Knack since 2012, he showed me an innovative way to use menus for filtering data.
As we worked on enhancing his existing application, Paul demonstrated a method of using standard Knack menus for filtering that I had never considered before. It was one of those lightbulb moments, reminding me that “every day is a school day!”
In the video, I walk through how you can set up these custom menu buttons for filtering within your applications. Not only does this enhance the user experience, but it also makes filtering data much more intuitive for users.
I hope you find this video helpful and that it inspires you as much as Paul inspired me.
I completely agree! It’s such a straightforward ‘no-code’ solution using Knack’s native features. I was genuinely surprised I hadn’t thought of it before!
ahahah amazing trick! I spent so much time trying to have both worlds of the filter tabs + the add filter… and so this is the solution! amazing. thank you!
This is one of those “it’s so obvious” tricks that stuns us all that we didn’t try it before. Thanks for sharing this. Another great video too.
I used this yesterday.
Yes - I think it would be very useful to be able to have custom filters but also have the ability to add others. Until this is an option the menu URL workaround is a good solution.
Also, the ability to create “or” filters in filter Defaults. Sheesh.
Actually make the filter experience consistent across all uses. A group of “All” conditions and a group of “Any” conditions would make life much better.
As a related topic, there is a trick about refreshing a parent VIEW (in the page) after editing/completing a form, etc.
I personaly do not like when the whole page is refreshed, since it HIDES the page for a 1s, making it a bad UX. I like the Trigger Action auto View refresh, but not aplicable to most cases.
The refresh trick: let say you have 3 views in a page, and you edit/create a child page in a View, if you click a tab menu or a title in a grid of this View, it refreshes only the corresponding view and NOT the whole page. Easy, no work, faster refresh, and nice UX.
I just found out that if you click the search button with blank field it also refreshes the view. ..without sorting, which it does by clicking on titles.
We talked in the community of a refresh button also. It is pertinent with One View page. If not, just for that you might not want to add a button for each view.
I whish there would be a way to tell this trick to users…
Hi @MichaelG - you can achieve this with KTLs keyword _cmr (close modal refresh). It will refresh data in all views on a page including detail views when a “modal” form is submitted. You can also achieve similar using _rvs ([Refresh Views after a Submit], if the form is not a popup modal. (Keywords · cortexrd/Knack-Toolkit-Library Wiki · GitHub))
The video below highlights the benefits of using the _cmr keyword when using modals as the table (grid) stays in place and just the data gets refreshed. I didn’t mention in the video that it also refreshes the parent views.
Yes that is the effect indeed. But I still did not put my brain looking at the cortexrd stuff, and your instalation tutorial video you told me about.
Last year I already logged a Request for this Knack feature. And not only refreshed the view, but also stay at the same position on the page where the click has been done, and obviously on the same page (in case of the tab menus it always send you to the first tab).
I think it is a very IMPORTANT feature for modern UX.
@Kara@JohnKaras please, inform us if this feature will be native in the NEXT GEN Builder. Tks!
It was one of those lightbulb moments, reminding me that “every day is a school day!”
