An easy and very useful trick with filter on grids.
Often you do not want to have too many columns in a grid, but still do want to filter through some of them. What are the alternatives?
You can delete those columns and use the Search through keywords in All fields in table. That works fine. But first you have to type the word, and then it might leave some other records with the same word in other fields.
A better and structured way is to keep those columns in the grid, but always hide them: Display Rule > Hide Value, and Hide empty columns. This way you can use the Filter instead of the Search, and it will show the fields of the hidden columns that you can select from. Way more UX.
hope it helps!
Interesting idea … hadn’t really thought of that approach. Simple and efficient.
Only issue would be if you have columns that are sometimes empty that you wish to keep visible.
Alternative is to use KTL, which allows you to exclude certain fields from being used as filters. Then allow filtering on all columns, and KTL will remove those that you have disallowed, giving you precise control over what can be used as a filter.
Didn’t know that filter fields selection functionality of KTL. Nice.
Do you know if KTL have something similar for multiple choice fields selection?
I don’t think so.
But i always set up multiple choice fields as connections to a choices table. That way you can filter however you wish, order them however you wish and add flags like active / inactive, what function the choices can be selected for, etc.
Takes 2 more minutes to set up but adds a huge amount of flexibility…
I take it back - KTL does have a “REMOVE OPTIONS” keyword which does this:
_ro=field, option1, option2…
Remove Options
Used in: Views
Supported options: Multiple Instances, ktlRoles, ktlCond
This is used in form views to limit the choices available to a user by excluding specified options for a given field.
Applicable field types include:
- Multiple Choices
- Booleans (such as Checkboxes, Radio Buttons, and Yes/No selections)
- Single and Multiple Selection dropdowns with fewer than 500 entries.
To the specified field, it will remove the listed options.
Example:
_ro=Sale, 50%, 75%
Will modify the Sales field by removing the 50% and 75% options, leaving others like 15% and 25% still available.
Video tutorial: none
2 Likes
That is an interesting way of doing. 
Amazing!! We’ll have to buid a monument to Norm!
I wish the Next Gen Builder includes very fast those very useful functionalities.
1 Like
I did a video on using connected objects as opposed to multi choice fields four years ago.
Multi Choice Fields - Knack Database
I think it’s unlikely that any of KTLs features will be in the Next Gen builder initially.
Yep, I saw it and saved it. Very very useful to edit multi option choices.
But I remember it as connected fields not objects.
So here is an example of what I use:
I can filter by whether its still an active option, what type of usage this option is intended for, and define the display order the way I need it to be …
