Spotfire Ideas Portal
ADD A NEW IDEA

Ideas

    Showing 752 of 4806

    show more information in data loading dialog

    Currently we can get below information in data loading dialog when opening analysis or loading data, \! filetype=Spotfire.DataFormat.Text; version=2.0; \! property=Name; category=Column; type=String; \! property=DataType; category=Column; type=S...
    about 4 years 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 7 years ago in Spotfire / Data Management 2 Future Consideration

    Parallel reload of multiple on-demand tables

    Parallel loading of data was added in TIBCO Spotfire 11.4, but reloading of multiple data tables (Data > "Reload all data") is still done synchronously in series. When you have several on-demand tables that you want to reload at once, it would ...
    about 4 years ago in Spotfire / Data Management 1 Future Consideration

    Overall overview of markings and Filter Settings

    When taking over a report from a colleague (who has left the organisation/company) it can take quite some time to find out all filters etc that has been applied. I would be very handy to have a page that can display all filters, data limitations a...
    about 7 years ago in Spotfire / Filters 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 ...
    over 9 years ago in Spotfire / Data Management 1 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 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...
    over 7 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...
    about 1 year ago in Spotfire / Data Management 0 Future Consideration

    Impact Analysis in Calculated Colomns

    hello Sometime we need to do some clean up in the calculated colomn, or delete an import colomn. Today, we must look at every calculated colomn to know where it is used. Could we have (like in Information link) a right click button to ask "Where i...
    over 8 years ago in Spotfire / Data Management 0 Future Consideration

    Provide driver to read TDV objects from Azure Synapse Analytics spark pools

    Way to achieve the idea: Provide a driver (which is similar to CSJDBC(8).JAR) to be used in spark code of Microsoft Azure Synapse Analytics Workspace. Benefit: It will allow us to access and transform the TDV objects in the Spark pool. In this way...
    over 4 years ago in Spotfire Data Virtualization / JDBC / ODBC / ADO 0 To be Reviewed
    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