Skip to Main Content
Spotfire Ideas Portal
ADD A NEW IDEA

All ideas

Showing 4303 of 4303

Coloring rule in cross table based on underlying data table

Coloring rules are based on the rows in the cross table (and not on the rows in the underlying data table) - Grand total values in a cross tables are aggregated from the rows in the data tables. The user is unable to create a coloring rule based o...
over 8 years ago in Spotfire / Visualization 1 Future Consideration

Support of SQL Complex Data Types (ARRAY, MAP, STRUCT)

In our databases (Oracle, Impala, ...) we use complex data types (ARRAYS, MAPS, STRUCTURES). Those data types are not supported today by Spotfire in-db connectors.
almost 8 years ago in Spotfire / Data Access 0 Future Consideration

Ability to copy/edit Data Source Information steps to another spotfire report with same data tables

Would be helpful if there is a option to copy all the steps that are perform in one data table when we dot Edit > Data Table Properties > Source Information steps to another Spotfire report which has the same data tables
over 7 years ago in Spotfire / Data Management 4 Future Consideration

Cloud Spotfire - Statistica integration

Cloud Spotfire users are interested in TIBCO Data Science and would benefit from integrating Cloud Spotfire and Statistica
over 3 years ago in Spotfire / Data Functions 0 Future Consideration

Allow MODs to work with more than one table like JSViz

It feels like Mods is the future of JSViz. Since JSViz provides support of working with more than one table, we are still using it to create custom visualization. If MODs did not have this limitation, we would be adopting Mods instead of writing c...
over 3 years ago in Spotfire / Mods 1 Future Consideration

Improve save when node in in state Disposed

I often see customers with errors when trying to save an analysis like:- Attempt to read from a node that is in state 'Disposed' There are various reasons for this but erroring and not allowing the user to save is not a good experience. Why not re...
over 3 years ago in Spotfire / User Experience 0 Future Consideration

Wildcard or partial string matches for Data on Demand

I'm trying to work with Data on Demand with "string" type fields. We have a large database of error logs, and are trying to search through the log text to find mentions of a specific substring that can appear in slightly different places within th...
over 1 year ago in Spotfire / Data Access 0 Future Consideration

Lock Map Zoom & Extents

Lock a zoom location totally custom; no changes on data marking and not possible for user to move
over 4 years ago in Spotfire / Maps 0 Future Consideration

Label Bar Chart by category Names

Instead of just showing the value of the bar also be able to show the category name so you don't have to hover over the bar.
almost 5 years ago in Spotfire / Visualization 4 Future Consideration

Change default encoding to Unicode (UTF8) when replacing data table in Spotfire using Ironpython script

refer to the support ticket - 01862613 We have code in place which replaces data table based on dynamic parameter passing for multi clustered sql data. This works perfectly fine in english. But since because the encoding cannot be done before load...
over 4 years ago in Spotfire / Data Access 3 Future Consideration