Spotfire Ideas Portal
ADD A NEW IDEA

All ideas

Showing 3890

Clear marking in response to filtering

Scenario Data Table with 2 rows, with 1 row marked. A filter is applied such that the marked row is filtered out; however, marking persists. Goal Clear marking for those rows that are affected by applied filter without the use of Data Function/Scr...
about 2 years ago in Spotfire / User Experience 0 Future Consideration

Option to display guidelines that track horizontally and vertically across visualisation charts

Could we have "on hover" guidelines that track a mouse movement over a chart and help the user to orientate his or herself against the X and Y axes' values? This is particularly for scatter charts. It would be great if we could also display the ex...
over 6 years ago in Spotfire / Visualization 0 Future Consideration

User Defined Keyboard Shortcut..

If user are able to define keyboard shortcut to Spotfire menu, it will be accessed by user easily and quickly.
about 8 years ago in Spotfire / User Experience 6 Future Consideration

Tiled markers for projections in map charts

Tiled marker shapes on scatter plots are very powerful for aggregating lots of data and showing distributed 'heat maps' of measures. Currently there is a limitation whereby they can't be used in map charts which use a coordinate reference system. ...
about 2 years ago in Spotfire / Maps 0 Future Consideration

Use (In-memory) Visualizations as input to Data Functions

WHAT: Enable the data currently displayed in a visualization to be sent to (any) Data Function, either automatically (when the visualization changes) or not. WHY: Much easier development of predictive analytic applications & easier ad hoc usa...
over 8 years ago in Spotfire / Analytics / Data Functions 3 Future Consideration

execute multiple Python/TERR data functions in parallel even all of them are from the same Analyst/WP/AS session

We have confirmed with TIBCO support that, currently as designed/implemented how the data function services work, all data function service(Python/TERR) invocations per analysis session are serialized. Also, there is no configuration to force seri...
over 1 year ago in Spotfire / Data Functions 1 Future Consideration

Support for in-memory star-schema relational model without requirement of Insert Columns

Support for 2+ tables in the same visualization. Note: The current functionality (as of 7.8 and earlier) supports two FACT tables in the same visualization, but not a FACT table and 1+ DIMENSION table(s). This enhancement request (Original enhance...
almost 8 years ago in Spotfire / Data Management 0 Future Consideration

Pages by for cross and data tables

Sometimes, having one separate table for each dimension of the data can be very useful. Having the option to display cross tables, but also data tables using the trellis option "pages by" could result in a very useful view on the data. Particularl...
over 7 years ago in Spotfire / Visualization 3 Future Consideration

Spotfire Server / Node Manager - Provide default service configuration for Automation Services and Web Player

In order to prepare the Spotfire Server / Node Manager upgrades, it would be very useful to be able to get he default configuration for Automation Services and Web Player. By having the necessary files prior to the upgrades, the administrator woul...
over 4 years ago in Spotfire / Installation 0 Future Consideration

Allow combination of stacked and side-by-side bar charts

Description: Spotfire allows stacked bar charts, with an aggregation method on the value axis such as a SUM or COUNT and a matching category on the category axis such as a name. If a developer wanted to have side-by-side bars on only a few bar se...
over 6 years ago in Spotfire / Visualization 4 Future Consideration
This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for Spotfire products and services. It is for informational purposes only and its contents are subject to change without notice. Planning to implement - generally 6-12 months out. Likely to Implement - generally means 12-18 months out. Copyright © 2014-2023 Cloud Software Group, Inc. All Rights Reserved. Cloud Software Group, Inc. ("Company") follows the EU Standard Contractual Clauses as per the Company's Data Processing Agreement. Terms of Use | Privacy Policy | Trademarks | Patents | Contact Us