Spotfire Ideas Portal
ADD A NEW IDEA

Data Management

    Showing 313 of 4795

    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 6 years ago in Spotfire / Data Management 0 Future Consideration

    Transpose whole data in the Data Table

    No description provided
    almost 10 years ago in Spotfire / Data Management 1 Future Consideration

    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 9 years ago in Spotfire / Data Management 2 Future Consideration

    Add Row Count to Data Canvas

    After replacing a data source and adding columns/rows, I often check the number of rows in the resulting data table to make sure it worked correctly. Since a lot of these functions are now available in the Data Canvas, it would be nice to display ...
    over 6 years ago in Spotfire / Data Management 1 Future Consideration

    Another problem with data loading in 10.3 - defaults to add rows to table when tables are different!

    I load a table into 10.3 from xlsx file. I load the same table, again, but in the xlsx load dialog, I remove the final two columns from the load by unchecking their checkbox in the xlsx load dialog. Spotfire tries to add rows to the existing table...
    over 5 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 8 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 8 years ago in Spotfire / Data Management 0 Future Consideration

    reload on-demand data incrementally

    Customer would like to be able to reload on-demand data incrementally. E.g. if condition A/B/C/D are marked and data are loaded based on that, (1) when changing marking to A/B/C/D/E, only load data E and append to current dataset (2) when removing...
    12 months ago in Spotfire / Data Management 0 Future Consideration

    Add an overview of actualy used fields to the data canvas

    Report builders often start out with a data table with as many fields as they can think of. When a report becomes stable it is useful to be able to easily identify the fields that are actually used in the report visualisations and transformations....
    almost 4 years ago in Spotfire / Data Management 2 Future Consideration

    Matching column window of ExensioYield is not really functional while it's so frequent for table operations.

    Hi Tibco supporter, Would you help to make Matching column window of ExensioYield more conenient, pls? We heard it's basic functions come from Tibco. In semiconduct testing business, we do have >2000 columns which have >60 char names i...
    almost 6 years ago in Spotfire / Data Management 2 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