Spotfire Ideas Portal
ADD A NEW IDEA

Ideas

    Showing 4195 of 4798

    Global CSS file for one Analysis

    We are currently working with a CSS file in our analysis files. There is no place where you can define a "global" CSS file that influences your whole analysis file which is what we need. When you use a CSS file the body of your analysis file is no...
    about 6 years ago in Spotfire / Scripting 0 Future Consideration

    View Access of Data Function should be restricted for other Spotfire Analyst User except Developer for particular report

    Hi Team, Is there any way to keep the data functions secure (where user who created the script only need to view it or modify the same and other user who have analyst license in the same server should not have access to view the function)? For exa...
    almost 4 years ago in Spotfire / Data Functions 2 Already exists

    Diagonal Axis labels

    Axis labels can only be horizontal or vertical. One better way to manage long axis labels is to have them diagonal as this would be best utilization of space and is more readable. This is already available in many other softwares.
    over 9 years ago in Spotfire / Visualization 2 Future Consideration

    all-in-one Spotfire Server installer

    Please bundle PostgreSQL in Spotfire Server's installer and make it possible to install a new environment with a few clicks. Currently one must do followings step by step, (1) install PostgreSQL (2) edit and run create_database.bat (3) install Spo...
    almost 4 years ago in Spotfire / Installation 0 Likely to implement

    Spotfire Analyst - Make available library metadata information

    I am looking for a quick and easy way to get the currently opened library analysis' metadata. Thinking about the File -> Document properties (where one would look "naturally" look I think), the Library tab or the Properties tab, none of these t...
    over 5 years ago in Spotfire / Library 0 Future Consideration

    Support of SQL Complex Data Types (ARRAY, MAP, STRUCT)

    In our databases (Oracle, Impala, ...) we use complex data types (ARRAYS, MAPS, STRUCTURES). Those data types are not supported today by Spotfire in-db connectors.
    about 9 years ago in Spotfire / Data Access 0 Future Consideration

    X/Y axis range (min/max) control with Custom Expressions

    It would be great if the user could input custom expressions within the x or y axis range boxes (either min or max or both). That would allow custom axis configuration with either logic (zoom to not show outliers, etc.) or with document properties...
    over 6 years ago in Spotfire / Visualization 0 Future Consideration

    Spotfire native connector for Bigquery need to restrict table list to the selected billing project

    Spotfire native connector (using OAuth credentials) need a new selection prompt for "Project" in addition to the existing "Billing Project" selection prompt, so that the connector returns only the list of tables the user is granted access to in Bi...
    almost 3 years ago in Spotfire / User Experience 2 Future Consideration

    Save any type of object in library

    Ability to save any type of object in library. So if I have custom data function or for that matter any custom extension whose state I want to save in library and make it sharable it is not possible.In case of data functions things like conneciton...
    almost 10 years ago in Spotfire / Library 1 Future Consideration

    Configure visibility of icons and menus in web client

    Application authors would like to control which web actions are available to consumers of a particular analysis. E.g. some don´t want tibbr and the collaboration tools to be visible, others wants to hide the filter panel or the bookmarks panel bec...
    almost 10 years ago in Spotfire 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