Spotfire Ideas Portal
ADD A NEW IDEA

Ideas

    Showing 4195 of 4798

    Ensure `data.table::patterns()` compatibility in future release

    data.table is preferred when working with large data sets for speed, and data.table::patterns() facilitates column(s) selection with regular expression, which is useful for concise code, as oppose to doing this as a separate line item.
    over 4 years ago in Spotfire / TIBCO Enterprise Runtime for R 0 Future Consideration

    Axes parameters and formatting is limited

    There is no way to adjust scales for logarithimc scales. provided sclaes look odd, not representative of log 10, small tick cannot be adjusted either. Scales for linear axed cannot be broken in (at least 2) segments. This "crunches " data is a poi...
    11 months ago in Spotfire / Actions 0 Future Consideration

    Overall custom style (CSS and JS)

    We would like to update he current HTML components and extend them. For this we want to have the option to enable a custom style sheet and javascript to be loaded with every report. Then the developer has the option to utilize this and we can over...
    over 4 years ago in Spotfire / User Experience 2 Future Consideration

    Searching chart information in Library

    I wish there were the ability to search for chart information (type, description, title..) in the library without opening Spotfire dxp. If we have a chart search function, we can refer to similar charts created by others and avoid creating duplic...
    over 1 year ago in Spotfire / Library 0 Likely to implement

    Provide API to retrieve information link details (SQL)

    Major data lineage tools (Informatica, ERwin) support scanning all BI tools such QlikView, Tableau, SAP, Cognos, but do not support Spotfire!! the stated reason from multiple vendor is Spotfire does not provide API to retrieve information link det...
    about 3 years ago in Spotfire / Data Management 0 Future Consideration

    Add auto-retry on failed data function call in case of 401/500 error from statsvc

    Problem: If Statistics services returns 401 or 500 error (that happens often enough for our users), current behavior of Webplayer (10.3) is to just fail. Usually it is enough to do manual retry, or do analysis F5 refresh but that is inconvenient f...
    about 5 years ago in Spotfire / Data Functions 0 Future Consideration

    SFDC (Salesforce.com) Custom Query

    Hello, We would like to have Custom Queries enabled for SFDC (Salesforce.com) when using the current connector. Presently, we can only import a report or table as a whole, without the ability to customize queries in SQL. This would simplify a lot ...
    over 1 year ago in Spotfire / Data Access 2 Future Consideration

    smooth the line curves in Spotfire

    The line curves in Spotfire aren't that smooth as the curves in Excel prompting management preference at times to dashboards with static curves in excel over the dynamic dashboards from Spotfire. Please make the line curves smooth to defeat the co...
    over 6 years ago in Spotfire / Analytics 3 Future Consideration

    Kerberos Delegation supported with OpenID Connect authentication setup

    In a hybrid setup with multiple legacy data sources on-prem and new data sources in the cloud, Spotfire should be able to request and "impersonate" the user with Kerberos. So the frontend supports OpenID Connect for authentication and the backend ...
    almost 5 years ago in Spotfire / Data Access 0 Future Consideration

    Allow Links to be added in title of Visualisation

    Is there any method to set the title of a visualization to a hyperlink ? We aim to direct the user to another tab of the same dashboard when the user clicks on the title of a visulisation. We checked the properties, we can set it to some Document ...
    almost 9 years ago in Spotfire / Visualization 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