Spotfire Ideas Portal
Imagine you have a text area with a document property selector. This selector is picking up unique values in some column. The user has previously filtered out many or most of these values, but they still show up in the document property selector. It should be possible to limit what's on display to only the filtered items. You can allow the document property selector to be associated with a filtering scheme.
You may think this is a minor thing, but think about why people are making document property selectors in text areas. They probably want to a convenient way for users to navigate the template and data. Having unwieldy document property selectors filled with items that aren't even there (because they were filtered) make it ugly and almost unusable.
In some circumstances, it's possible to create a calculated column that is a duplicate of some other column with some values nulled out. You can set your doc property selector based on this calculated column. However, with large data sets, this leads to a lot of wasted memory.
2
Future Consideration
Hi Jose, this idea represents the ability to have limit the "unique values in column" that are presented to the end user that is going to select a value to only the values that are present in the current filtering. As Spotfire works right now it will show all values present in the data, even if many of those values have been filtered out using filters.
I am not sure if it is related to the idea, but I was facing a similar issue and will post it as a new idea. But before doing so, please let me know if limiting auto populated Spotfire controls by filter schemes, markings or expression is related to this idea.
The attached image represents its functionality
Document properties should be able to hold any calculation and limit by filtering or marking, just like calculations in text areas can. Right now we are using simple output = input R scripts to do this, but that seems silly. If only there were a way to set a document property calculation without using a script.
Can we extend this to not just filtering in the text area using document properties but to everything in the filter panel.
Consider this use case - The range filter by default has a range from -100 to 100. however, based on other filter selections, the actual filtered range (which shows up in blue) is just from 99 to 100. In this case, the scroll bars become unusable unless the range auto - adjusts.
I'm asking for each filter type (especially range filter) to have an option to auto adjust based on other filter selections. This is very useful especially when dealing with filtering on columns that have outliers that screw up the default ranges.