Spotfire Ideas Portal
ADD A NEW IDEA

Spotfire

Showing 4083

Make Spotfire.Dxp.Data.DataOperations.DisplayName read/write

The Spotfire.Dxp.Data.DataOperations.DisplayName IronPython API is read only. Make it read and write so the data operation can be renamed programmatically or from the GUI This idea is somewhat related to https://ideas.spotfire.com/ideas/TS-I-7195 ...
5 months ago in Spotfire / API 0 Future Consideration

use parameter as identifier in Information link SQL

From time to time, we receive requests from our customers that they want to load data from database where table name is dynamic, e.g. on demand load data from different tablenames all of them have the same column structure. Unfortunately currently...
5 months ago in Spotfire / Data Access / Information Services 0 Future Consideration

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

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

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

Add line per bar based on expression in bar chart

Currently it is only possible to add a line in a bar chart which is shown over the full width. It would be nice to be able to draw a line in/at every bar. The the height of the line can be set with an expression. Examples:I've a stacked bar with...
over 8 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

Control default preference for Document Properties

With an analysis open in the Spotfire Analyst client, go to Edit > Document Properties > Library tab There are 5 checkbox options, all checked by default. I would like the ability to control the default settings for these 5 checkboxes in Ad...
over 8 years ago in Spotfire / System Administration 0 Future Consideration

Spotfire Analyst - Add more options for opening Spotfire Analyst from protocol call

Opening Spotfire from Spotfire.Dxp.exe or tibcospotfire:server:* does not provide the same functionalities. Referring to the following articles: https://community.tibco.com/wiki/tibco-spotfire-analyst-command-line-parameter-reference https://docs....
over 4 years ago in Spotfire / User Experience 0 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