You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I discussed and reviewed this with @amcclain and we came to the conclusion that adopting our client's suggestion for our Column Filter Values tab to behave more like Excel's Column Filter would be a good improvement.
The client's suggestion was made after using a Column Filter configured to show the "Apply Filter" button (commitOnChange: false), so the following guidance definitely applies to that configuration, but I think this improvement could be made also to the Hoist Column Filter when it is configured to be applied automatically (commitOnChange: true - no Apply button showing).
Excel does not appear to offer a Column Filter configured for commitOnChange: true , with no "OK" button.
The better experience we see in Excel is that the user does not need to pre-uncheck all of the available rows in the Values grid before typing into the filter field. The user can just type into the filter field, and then hit OK and the grid will be filtered by the values that appeared in the Values grid. When a user starts typing in the filter field, the "Select All" checkbox turns into a "Select All Search Results" checkbox, and an additional "Add current selection to filter" checkbox is inserted beneath it.
In Hoist, in order to filter by all of the results that typing in the filter field produced, a user must first uncheck the 'Select All' checkbox, then type their search string into the filter field above, and then check "select all" or the individual values he wants to filter on, and then hit "Apply Filter". It is not as intuitive, and users often need to be shown how to perform this sequence.
Please reach out to me if you would like a demo of the differences that I attempted to describe above. These UIs and their use are not the easiest to describe and attempts to do so do not make for the most exciting reading, to be sure.
Excel Column Filter
Hoist Column Filter
The text was updated successfully, but these errors were encountered:
I discussed and reviewed this with @amcclain and we came to the conclusion that adopting our client's suggestion for our Column Filter Values tab to behave more like Excel's Column Filter would be a good improvement.
The client's suggestion was made after using a Column Filter configured to show the "Apply Filter" button (
commitOnChange: false
), so the following guidance definitely applies to that configuration, but I think this improvement could be made also to the Hoist Column Filter when it is configured to be applied automatically (commitOnChange: true
- no Apply button showing).Excel does not appear to offer a Column Filter configured for
commitOnChange: true
, with no "OK" button.The better experience we see in Excel is that the user does not need to pre-uncheck all of the available rows in the Values grid before typing into the filter field. The user can just type into the filter field, and then hit OK and the grid will be filtered by the values that appeared in the Values grid. When a user starts typing in the filter field, the "Select All" checkbox turns into a "Select All Search Results" checkbox, and an additional "Add current selection to filter" checkbox is inserted beneath it.
In Hoist, in order to filter by all of the results that typing in the filter field produced, a user must first uncheck the 'Select All' checkbox, then type their search string into the filter field above, and then check "select all" or the individual values he wants to filter on, and then hit "Apply Filter". It is not as intuitive, and users often need to be shown how to perform this sequence.
Please reach out to me if you would like a demo of the differences that I attempted to describe above. These UIs and their use are not the easiest to describe and attempts to do so do not make for the most exciting reading, to be sure.
Excel Column Filter
Hoist Column Filter
The text was updated successfully, but these errors were encountered: