When filtering with != or <>, do not remove null/empty values unless it was specified.
When the condition for != or <> is filtered on, it should not filter out null/empty values unless it was specified in the condition. For example, if there is a field called "Number" with a list of numbers 1,2,3,4,5,6,,7,8 (null between 6 and...
over 1 year ago
in Spotfire / Filters
1
Future Consideration
Public API to check/uncheck the "Show notifications about mismatches" option
When programmatically creating visualizations with two or more tables, it can be that the specified ColumnRelation(s) are enough to properly link the data but that not all columns involved in the visual are matched, i.e. the visual and tables are ...
about 4 years ago
in Spotfire / API
0
Future Consideration
Would it be possible to add an lemmatization function in the text mining node. This would be greatly beneficial and ensure competitiveness of TM functionality with open source packages.
Inconsistent user input format for color specification in different parts of the product:
• RGB inputs for
• Visualization color schemes
• Text area font colors and control font colors
• HEX inputs for
• “Edit Custom Theme…” dialog
We should provi...
Other BI platforms allow for email by clicking on an icon. It would be useful to have the same in Spotfire so that when we are given an example of a dashboard to reverse engineer, we can add that functionality. The lack of it gives the appearance ...
over 1 year ago
in Spotfire / Actions
2
Future Consideration
Please improve the error messges for failed iron python scripts. For example when a script triggers another script or changes a document property that triggers another script, it is not clear in which script results in giving in an error.