Spotfire Ideas Portal
ADD A NEW IDEA

All ideas

    Showing 4800 of 4800

    Hide Repeating Hierarchy Levels

    Flat ragged hierarchies often repeat values at lower levels due to different drill down paths. It would be very nice to have the options to hide levels if the parent has the same value. Currently I have to click down through many repeating levels ...
    about 9 years ago in Spotfire / Custom Expressions / Filters 0 Future Consideration

    add support of LONG BINARY type from Vertica

    Customer is asking for support of LONG BINARY type from Vertica. Currently only BINARY/VARBINARY is supported by Vertica connector. They use BINARY/VARBINARY/LONG BINARY in Vertica to store images, however both BINARY and VARBINARY are limited to ...
    almost 2 years ago in Spotfire / Data Access 0 Future Consideration

    Hierarchical sorting in Cross Table

    When looking at data in a hierarchical cross table with multiple headers and sub-totals it is sometimes useful take the hierarchy into account when doing the sort. E.g. For a grouped table that show the sales of different products by customer one ...
    almost 2 years ago in Spotfire / Visualization 0 Future Consideration

    Add section to themes to configure buttons

    I would love to see a section added to themes for formatting the buttons in terms of button color, border, font and size. As the software is currently designed, if you want to reformat a button, you have to do it individually, which is time consum...
    about 9 years ago in Spotfire / Text Area 0 Future Consideration

    Embedding Data Functions

    We use Data Functions from our server library to quickly add features to new DXP files. The issue we are having is once you add a data function to a new DXP file it keeps the server path. If someone make a change to the function and then saves, it...
    about 9 years ago in Spotfire / Analytics / Data Functions 0 Future Consideration

    "Enterprise Adhoc Analysis with Input data" node support more complex logical statements

    Enterprise Adhoc Analysis with Input data node should support more complex logical statements like (Condition A and Condition B) OR (Condition C and Condition D)
    over 7 years ago in Spotfire Statistica 0 Future Consideration

    reset browser after analysis is close on Analyst

    Currently if one defines a global variable using JavaScript in Text area, the global variable remains there even after analysis is closed. The same applies if global timer is defined, it won't stop running until Analyst is close. As per support, t...
    almost 2 years ago in Spotfire / Scripting 2 Will not implement

    Option to execute defined output settings, when enterprise report is run manually via Statistica Server

    Some users use Statistica Server to manually execute enterprise reports. At the moment, the set output option (e.g. send E-Mail, save Report in file system) are ignored. It would be good to have an option to follow these settings if needed (analog...
    over 7 years ago in Spotfire Statistica 0 To be Reviewed

    Rendering Images in Cross Tables

    Currently, image rendering is possible in tool tips and in tables. In a cross table, because of required aggregation, images cannot be rendered. If an aggregation option such as 'First()' is used, there is no reason why the image cannot be rendere...
    about 9 years ago in Spotfire / Visualization 1 Future Consideration

    Allow the import of TIMESTAMP WITH LOCAL TIME ZONE datatype from Oracle database

    Using Add Data tables option , I am trying to add Oracle 12 DB table but one Timestamp table field having datatype as "TIMESTAMP (3) WITH LOCAL TIME ZONE" is not visiable / showing up in Spotfire UI This is apparently not supported and it would be...
    over 7 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