Spotfire Ideas Portal
ADD A NEW IDEA

Data Management

Showing 300

Enhancement Request - Officially Support use of IN Operator

Request for Spotfire to "officially" support the use of the IN operator in the Spotfire Expression Language. For example:CASE WHEN COLOR IN ('RED', 'BLUE', 'GREEN') THEN TRUE ELSE FALSEEND I've written code that uses IN () and it *appears* to work...
about 8 years ago in Spotfire / Data Management 2 Future Consideration

Enable mass rename of columns during the transform data process

Multiple data tables are often joined using the "Add as columns to" option. Often, the data sets being appended have the same value column names (ex. $, $ YA, Units, Units YA) which results in the subsequent data value columns having ([%C (n)]) or...
about 4 years ago in Spotfire / Data Management 0 Future Consideration

Manual setting of primary key column (Impala, DB2, etc)

When using external data, detail visualisations need a primary key in the datasource for markings to be applied. In case of views or custom queries, the resultset has no primary key defined on the database level. Would be great when we could selec...
over 7 years ago in Spotfire / Data Management 2 Future Consideration

Add summary rows to table or visualization

In Spotfire, it is currently possible to add additional columns with calculated columns. I need to be able to do something similar with rows. I am working with financial data -- revenue, expenses, etc. Most of these reports are done in cross table...
over 7 years ago in Spotfire / Data Management 0 Future Consideration

add an option to not show "Missing File" dialog if data source's loading setting is set as "New data when possible" on Analyst

Please add an option to not show "Missing File" dialog (go on loading embedded data without asking) if data source's loading setting is set as "New data when possible" on Analyst, preferable a data table/data source level setting (Data canvas), an...
over 1 year ago in Spotfire / Data Management 0 Future Consideration

Support extremely wide data sets

Spotfire is excellent when working with wide datasets that can contain thousands or even tens of thousands of columns. In some situations, datasets can be extremely wide with millions of columns, which sometimes causes performance and UX issues. I...
over 1 year ago in Spotfire / Data Management 0 Future Consideration

Data Canvas UX: Column datatype formatting inside Data Canvas

See attachment The Data Canvas is a great place to manage, wrangle, cleanse, and enrich data. However, the options for formatting column data types are not found within it. You must leave the canvas and go to the Data Panel column handler then s...
about 6 years ago in Spotfire / Data Management 2 Future Consideration

Numeric equality issues when using a Single Real column

When doing comparisons against a single real column, the static value entered is not auto cast to a single real. This results in rather odd behavior such as the value 1.1 in a single real column != the user entered value of 1.1 If for example. I h...
about 5 years ago in Spotfire / Data Management 0 Future Consideration

Visualization data as data table in Spotfire

Often we need access to the aggregated data from a visualization. E.g. for an external tool; or for reporting; or for input to a data function. We should have the ability to have the aggregated (plot) data available as a data table in Spotfire. It...
about 6 years ago in Spotfire / Data Management 0 Future Consideration

Setting for Case sensitivity

Currently Spotifire is Case Sensitive which makes aggregations at certain level harder to manage. While you can do all sorts of string manipulation it would be nice to have a setting to turn on/off case sensitivity. For example , if you aggregate ...
about 8 years ago in Spotfire / Data Management 1 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