Spotfire Ideas Portal
ADD A NEW IDEA

Ideas

    Showing 752 of 4806

    SQL JSON parsing in TDV should be improved

    Using JSON_TABLE is cumbersome, and there are no examples on how to do JSON parsing in a simple way using a transformation (can it even be done?). As an example, Postgres has a simpler syntax allowing queries like this : SELECT id, data::json->...
    about 2 years ago in Spotfire Data Virtualization / sql support 0 Future Consideration

    Add a Licence to allow saving a DXP with Stored data

    We have users working with very large datasets and we wish to stop them being able to save these files to the Spotfire library with the data stored in the dxp file
    over 6 years ago in Spotfire / Data Management 0 Future Consideration

    change filter type of multiple columns with a few clicks

    Customer wants to change the filter type of multiple columns with a few clicks. Currently one has to change the filter type of each column one by one, sometimes there are hundreds of columns that need to be changed and it's quite time consuming.
    about 2 years ago in Spotfire / Filters / User Experience 0 Future Consideration

    Update TDV to centos 9 from centos 7

    We want to upgrade TDV to centos 9 from centos 7; as per Tibco support below response support team, I am creating this idea. Please let us know the timeline for supporting Centos 9. Unfortunately, at this point, none of the available TDV versions ...
    about 2 years ago in Spotfire Data Virtualization 1 Will not implement

    Doc ER (Install Guide) - Add the Studio installer name

    The following section in Install guide is missing the Studio filer name. An example of the installer name / syntax would help navigate which file to download for Studio installation on Windows. https://docs.tibco.com/pub/tdv/8.8.0/doc/pdf/TIB_tdv_...
    about 2 years ago in Spotfire Data Virtualization / management 0 Future Consideration

    Seperate JVM for cached objects

    Currently, DV runs with single JVM for all server threads, user requests, caching,etc. and causing too high HEAP requirement, custom GC settings and unrecoverable exceptions. This is causing frequent restarts (due to node shunned alerts) and somet...
    over 6 years ago in Spotfire Data Virtualization / performance 1 Needs Info

    Cache target should not be visible to the user group

    Cache target should not be visible to the user group as there is a tendency of direct analysis on those cache tables rather than using those through applications. This will avoid load on the cache system
    about 2 years ago in Spotfire Data Virtualization 0 Planning to implement

    Display Row Counts instead of Data Size while loading Information Links in Spotfire Analyst

    Previous versions (up to v7.5) of Spotfire Analyst had display of row numbers while loading Information Links in display window. Spotfire 7.11 shows loading of data in terms of data size being processed. This is not beneficial as Developer does no...
    over 6 years ago in Spotfire / Data Management 1 Future Consideration

    "Undefined" Data type in document properties on DXP

    Is it possible to create "Undefined" data type document property in DXP as it is available in Information designer on "Parameters" section. Use: 1.If Spotfire can replace the parameters in information link as is for example with no string formatti...
    almost 9 years ago in Spotfire / Data Management 5 Future Consideration

    Restrict specific service id in one of the node in a TDV cluster

    Restrict specific service id in one of the node in a TDV cluster . We want to restrict some service ids in some tdv nodes in same cluster. The current feature of removing privilege's or RBS or work load management get sync across all the nodes. Re...
    about 2 years ago in Spotfire Data Virtualization / access control 0 Unlikely to implement
    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