Spotfire Ideas Portal
ADD A NEW IDEA

Ideas

    Showing 636 of 4816

    Bulk Data Source Path Replacement

    Currently, we use files located on a Windows shared folder as our data source. Whenever our system is updated and the shared folder path changes, we are forced to manually update the absolute path for every single analysis file. This process is ex...
    7 months ago in Spotfire / User Experience 0 Future Consideration
    150 VOTE

    Use a Calculated value in a Property

    There are at least three areas that I can currently create a calculated value. Text Areas Inputs for Data Function Graphical Tables However, if I want to have a Document Property to contain a calculated value, I can't do it without running some ...
    almost 10 years ago in Spotfire / Custom Expressions 12 Future Consideration
    105 VOTE

    Save expressions /formulars in a central location in the library

    In the section where you can insert calculated columns you can re-use previously used expressions. This is a handy feature. However, it shows all recent expressions. There is no option to include only the ones you want to be remembered. Hence Spot...
    about 7 years ago in Spotfire / Custom Expressions 2 Future Consideration
    118 VOTE

    Calculated Columns that Filter With Data

    Calculated Columns are powerful but often not useful if they don't recalculated based on filtered data. We've developed scrips to flag filtered records and calculate over that flag but this requires the user to click a button every time they filte...
    over 9 years ago in Spotfire / Custom Expressions 1 Future Consideration

    High DPI support

    When using the Spotfire Analyst client on High DPI screens now it runs in high DPI compatibility mode: all pixels are scaled to larger pixels. Adding native high DPI support would allow the visual splendor of Spotfire to shine so much brighter. Wi...
    about 2 years ago in Spotfire / User Experience 0 Future Consideration

    Don't execute data functions when required input data is empty

    Many data functions you want triggered from markings. However, when nothing is marked, empty inputs are sent to the DF which causes errors. So you have to create specific error handling code for TERR to detect # rows for input and send out empty d...
    over 5 years ago in Spotfire / Data Functions 4 Future Consideration

    Cache job auto-restart upon failure

    We would like the option to automatically reattempt a cache job when it fails. We have some public api data sources that randomly fail from time to time, and they succeed if you just restart them. It would save us time and failure alerts if they c...
    about 6 years ago in Spotfire Data Virtualization / caching / data movement 2 Future Consideration
    107 VOTE

    Reverse Sort order option for date columns

    As a user, I want to be able to sort columns including various date formats in order to view data in chronological or reverse chronological order. Should support major date formats including: January 2012January 2 20122 January 20122012 January 21...
    about 10 years ago in Spotfire / Custom Expressions 1 Future Consideration

    Add tabs on visualizations

    We have pages that contain visuals. We can duplicate or create new pages. We need tabs that contain visuals within visuals so that many visualizations can be located on the same place as one visual that can be cycled through tabs. See attached ima...
    almost 3 years ago in Spotfire / User Experience / Visualization 0 Future Consideration

    Manage Model objects between data functions

    One data function used to train a model, another used to predict with new data. Need easy way to retain model between data functions. Using the "pickle" package works but is but cumbersome. Perhaps "Analytics Models" could be used.
    over 3 years ago in Spotfire / Data Functions 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