Spotfire Ideas Portal
ADD A NEW IDEA

Spotfire

    Showing 3822

    Please add a progress bar on the Spotfire Analyst client when downloading updates

    It would be useful to have a progress bar when downloading updates so that users can see if any data is actually being downloaded. On many occasions there have been large updates which give the false impression that the update process is dead whic...
    about 9 years ago in Spotfire / Installation 0 Future Consideration

    Reliable distro files naming convention

    We had invested a lot of effort into building automations that would allow upgrade Spotfire quickly. Every such upgrade process starts with new distro files as inputs. But for some reason, distro filename convention keeps changing and it breaks o...
    about 1 year ago in Spotfire / Installation 0 Future Consideration

    Allow Lines and Curves to use Column Matches

    See attached file. We have an ongoing issue where an (Empty) value in a Data Table Relation does not allow us to plot lines, while this exact same function works for custom expressions. The reason I got from support is basted below. This would be ...
    about 9 years ago in Spotfire / Visualization 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 9 years ago in Spotfire / Data Management 1 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

    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

    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

    Expand the ExportDataToLibrary API to include the options available in the UI

    When exporting data to the library through the UI you have the option to apply filtering or marking. When using the API these options don't exist - you can simply save all data from the table.
    about 8 years ago in Spotfire / API 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
    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