Spotfire Ideas Portal
When using a Radio Button or Listbox filter the "All" and "None" options are always available. It would be helpful if there was a way to remove these so the report user didn't have the option to select either of them.
| Implemented in | 11.2 |
Starting with Spotfire 11.2, you can now remove the (All) and/or (None) options from the item, list box, and radio button filters.
You can learn more about this in the What's New in Spotfire 11.2 page here: https://community.tibco.com/wiki/whats-new-tibco-spotfirer-112#toc-11
1
Implemented
@Holger, I think your request makes sense from a dashboard design perspective. May I ask you to create a new idea for this?
@Arnaud, I would think removing "all" is an explicit decision for the design of the dashboard. Therefor this message is confusing. Maybe you could add possibility to define default value for the selected value of the filter? Or the reset value could be the one which would selected when the dashboard was saved? Maybe modifying the info message and making it more explicit what filter is still set to what value could be useful. In the current way I fear we are confusing users.
@Holger, thanks for the feedback. I understand your point.
If we get the first radio button option selected it means there is still a filter applied. We think this could also lead to confusion for end users.
We want to use this feature to hide "(All)" from radio filter, but then the reset filter button throws an error.
I understand the error message, but is there anything we can do to prevent the error and e.g. instead of "(All)" get the first radio button option selected?
Otherwise this feature to hide "(All)" is not really useful and confusing for end users.
@neil @dave thanks for the suggestion but this is a wholly unsatisfactory workaround. Dave, I am a developer so best not to assume, and please do not disregard other people's ideas. This solution does not allow the filter to live in the filter panel where it needs to be for a production application. We cannot have random filters sitting around in text areas. Second, that means you would have to then apply that data by expression to every single visualization in the module which is very difficult to maintain and can cause numerous other issues. Thirdly this prevents the proper data being fed to data functions.
Thanks @Neil Kanungo. This does show that there is generally some way to achieve the requested behavior, but it is not always obvious to users to think like a developer. they are often simpler in nature and they may not have the product affinity and dedication to work though this or know how it is done in other tools and expect to be able to do it here too.
A workaround I currently use is a property control. You can set a document property value, then set the property control slider to only use "unique values" in your column, then in your visualizations us a limit data expression that filters out that document property.
If you'd like to see in action, this is currently in use on TIBCO's COVID19 Dashboard (www.tibco.com/covid19) on the "Overview" pages that let you slide through the date.
Yes. The Filtering Scheme Properties (where the author can configure options for each filter) is the ideal place to put it..
"All" and 'None' both have there value based on data sets and how tables may be related but we should be able to select as a filter property to show or not the "All" or "None" options.
This is a top idea for 4 years. Any updates? How hard could this possibly be tibco? Come on!
Radio buttons are design for selection one entry at a time. I agree "all" and "none" should have never been there.
I'm looking for that since months...
Why is the "None" option included at all - as this will by definition always filter out all data?