Spotfire Ideas Portal
ADD A NEW IDEA

Ideas

    Showing 4224 of 4805

    add API to load data via data connectors

    Please add API to load data via data connectors, similar to Spotfire.Dxp.Data.Import.InformationLinkDataSource but usin data connectors. Currently below API is for loading data from database using the old technology(not recommened any more) Spotf...
    about 4 years ago in Spotfire / API 0 Future Consideration

    Using Open source Octave as an alternative to Matlab

    I been working with a programing tool called Octave. The language is almost identical to basic Matlab. The discriminating difference is that Octave is open source and free. Octave offers similar performance efficiencies to Matlab.
    about 5 years ago in Spotfire / Data Functions 0 Future Consideration

    Adding Data from multiple tabs in excel at one time

    There are instances where you receive daily details on each tab of excel which runs into 30 tabs. So the data input should be designed in such a way where we can input all the details at one time rather than inputting the data 30 times as all the ...
    over 8 years ago in Spotfire / Data Access 0 Future Consideration

    Deploying a new deployment area to Spotfire client removes the older packages and modules

    Hi Developers, Switching to a new deployment area through Spotfire client startup removes the older packages (modules) and replaces them with the new packages into the Modules folder. This makes switching between versions not possible since every ...
    about 6 years ago in Spotfire / Installation 2 Future Consideration

    Delimiter options for Automation Services Data Export

    From within Automation Services, we can currenly only export to CSV using the Comma or Semi-Colon delimiter. Having more delimiter options would be incredibly useful for us - especially the ability to use the Pipe ( | ) delimiter.
    about 5 years ago in Spotfire / Export 0 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

    Unable to format export file name

    Unable to format export file name, currently it always take Dxp name as file name. we need feature to have customized file name. e.g ABC_yyyy_mm_dd.csv Possible right now: dxp_name.csv , dxp_name(1).csv
    over 9 years ago in Spotfire / Export 2 Future Consideration

    Use List Document Property in SQL "IN" Statement within Custom Expressions

    It would be useful to be able to pass a list type document property (e.g. "String List", "Date List", etc...) into a SQL "IN" statement in a custom expression or calculated column. This can then be used to provide input for options for consumer us...
    about 5 years ago in Spotfire / Custom Expressions 3 Future Consideration

    Add ability to duplicate controls in text area

    We often use text areas to create great looking dashboards, but having to configure all aspects of multiple similar Spotfire control elements from scratch can be time consuming. The ability to be able to duplicate an existing control and then edit...
    over 8 years ago in Spotfire / User Experience / Visualization 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
    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