Spotfire Ideas Portal
ADD A NEW IDEA

Ideas

    Showing 4254 of 4816

    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

    Combine summary table + data in analysis + graphical table

    The summary table is a nice and quick tool to get an overview of all columns in a data table. However, it lacks a few features which is why we end up re-inventing the wheel with adding a data function and subsequent visualization set-up. Many of t...
    9 months ago in Spotfire / Visualization 1 Future Consideration

    Enhanced Legend Design - Gradient Color

    The color legend on maps, bar charts, scatter plots etc.. could be improved for both discrete and continuous metrics. It could look 10 times more professional and could increase user experience with an easier design to read.
    over 2 years ago in Spotfire / Visualization 1 Likely to implement

    Limit file size returned from data functions

    In the configuration options for e.g. an R data function you can limit the size of the input files send to the R-service and this is helpful to protect the infrastructure. spring.servlet.multipart.max-file-size spring.servlet.multipart.max-req...
    3 months ago in Spotfire / Data Functions 0 To be Reviewed

    Incremental updates of data in-memory

    I want to only pull the incremental updates into memory via the schedule updates. As they have a few analysis set for Schedule Updates that are very large, but the amount of data that is new is relatively small, so pulling the entire data set ever...
    about 10 years ago in Spotfire / Data Access 2 Future Consideration

    Location invariant value formats in expressions

    *Goal:*As an author, I need to control the exact format of my data so that I can properly configure the rest of my analysis. Regional language and cultural settings are client dependent and therefore dates and decimal separators change depending o...
    about 10 years ago in Spotfire / Custom Expressions 2 Future Consideration

    Allow grouping of TERR/Python nodes using resource pools like the WebPlayer nodes

    Routes allow administrators to very easily assign users/groups to specific WebPlayer instances using resource pools. Unfortunately this mechanism is not available to TERR or Python nodes. It makes complicated to try to split resources based on gro...
    over 2 years ago in Spotfire / System Administration 0 Future Consideration

    Crosstable aggregate function for totals

    I need to show the average of the row values in a cross table. The only option is a total as a sum, but what I really need is the average. In Tableau I could do this easy, when will Spotfire add this?
    almost 5 years ago in Spotfire / Custom Expressions 4 Future Consideration

    Improved API to read metadata and lineage for library items

    From my external application, I want to call a Spotfire Library API (preferrably REST) to read metadata for library items and their dependencies. This can be seen as an enhancement to the current LibraryService API (SOAP), but more detailed met...
    over 2 years ago in Spotfire / Library 0 Likely to implement

    Bulk-changes of dxp files

    When you need to make a change in a dxp/analysis file - e.g. change a connection string to point to a new location, or fix a bug in a script - that's usually easy, but often, you want to make the same change in any affected dxp file (there might b...
    over 3 years ago in Spotfire / Library 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