Spotfire Ideas Portal
ADD A NEW IDEA

All ideas

    Showing 4800

    Improve JDBC Query operators and Data constructs

    Query JDBC operator should behave/look as close as it could to "In memory tables". One case is the one stated in "SB-44976 JDBC Query Op Output Settings cannot use aggregate expressions" . Another would be that for an In Memory table we can define...
    about 7 years ago in Spotfire Streaming 0 Unlikely to implement

    Allow access to HttpServletResponse from the custom authentication APIs

    We currently use the Authentication Filter capability (which has been deprecated) of Spotfire to implement a couple of features that don't appear to be possible with the CustomAuthenticator API: In certain situations we'll redirect the browser to...
    about 7 years ago in Spotfire / API 3 Future Consideration

    Spotfire as a Service

    Spotfire Web should behave as a service. We should be able to load and query a Spotfire analysis via an external API and query it for data, results from aggregated visualisations, visualisation images, etc.. This means that we would be able to use...
    about 7 years ago in Spotfire / API 0 Future Consideration

    Add ability to programmatically determine what objects are included in a cache policy.

    Using a policy has exponentially reduced the time to complete the full cache refresh (from ~ 3 hours to just over 1 hour). However, there is no way to determine which views/objects have been added to a policy, thus managing the cache refresh proce...
    about 7 years ago in Spotfire Data Virtualization / caching 0 Future Consideration

    Ability to increase header size of DE Input for specifically for Characteristic/Label

    It would be helpful to \increase the characteristic/label header length alone (so it doesn't warp to 2 lines, see screenshot) without increasing the input area without having to increase it globally for all DES via application settings.
    about 7 years ago in Spotfire Statistica 0 Future Consideration

    Support Integration with Alation Data Catalog Tool

    My company is using Alation for Data Catalog, it would be great for Spotfire to retrieve field definitions from Alation API, so they could be exposed on Spotfire reports. That tool also does not support importing the Information Links and Report D...
    over 3 years ago in Spotfire / Library 0 Future Consideration

    Percentile() - allow different calculation types (as in TERR) for calculated columns

    TERR allows 3 discrete and 6 continuos calculation variants for quantile() which ends in different results. It can be controlled by optional 3rd parameter. Default value is 7. However expression language used for calculated columns only supports t...
    over 3 years ago in Spotfire / Data Functions 0 Future Consideration

    Remove the selected columns from 'Available Columns' in 'Select Columns' window

    when selecting multiple columns it would be much easier if the already selected columns will not appear in the 'available columns' list
    about 7 years ago in Spotfire / Filters 1 Already exists

    use value in document properties on filters

    We have many customer asking for this. Typically customer uses input field or drop down list to select a value, then he wants to use this value in filters. Currently filters can only by set by fixed values, customer wants to use values from docume...
    over 3 years ago in Spotfire / Filters 0 Future Consideration

    Enhance / choose the geo-coding service used in map chart search

    There should be an option for analysts to use alternate address look-up tables / geo-coding services to search and limit geospatial address information displayed in map charts.
    over 3 years ago in Spotfire / Maps 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