Spotfire Ideas Portal
ADD A NEW IDEA

All ideas

Showing 4363

Mobile: add an additional password r fingerprint for accessing the mobile app

All the data on the app is only protected by the 4 digits pin code of the IOS device. This is not compliant to the strict security rules of AkzoNobel. Will it be possible to develop an additional password (with about 8 positions and different sign...
almost 8 years ago in Spotfire / Mobile 0 Future Consideration

always show top/upper level category value when scrolling down in cross table

Lets say we have a cross table with vertical axis configured with "Position"=>"Team" (baseball data), since there are lots of teams inside 1 position, when scrolling down, the value of "Position" on top is not visible any more. Customer wants t...
almost 2 years ago in Spotfire / Visualization 0 Future Consideration

Ability to use custom IDEs with integrated support for the Spotfire API

It would be great to develop IronPython code for Spotfire reports in another IDE (for instance Visual Studio Code) and retain the ability to reference Spotfire visualization elements (e.g. a table, scatterplot, or visualization title)
almost 8 years ago in Spotfire / Scripting 0 Future Consideration

PDF Multiple DXP Files

We are trying to figure out a solution to create one pdf file across several DXPs (reports). For example, Report A has 3 tabs and Report B has 2 tabs. I would like for there to be an option to export both Report A and Report B to get a total of 5 ...
about 6 years ago in Spotfire / Export 0 Future Consideration

Show path for the search items like information link in information designer.

Right now when someone try to search for an information link with some part of its name like *well* on information designer it doesn't return the path, again we have to open Library admin do same thing there and find the path then come back again ...
almost 8 years ago in Spotfire / Data Access / Information Services 2 Future Consideration

Support JSON data type of PostgreSQL

PosgreSQL supports JSON format from version 9.3. Unfortunately, Spotfire doesn't support JSON data type when working with a PostgreSQL database like the following link. https://docs.tibco.com/pub/sfire-analyst/7.11.0/doc/html/en-US/TIB_sfire-ana...
about 7 years ago in Spotfire / Data Access 0 Future Consideration

Option to restrict Embedded Data at User Level/Group Level/Report Level

1) To control the size of data and to decrease load on the server by restricting at User Level/Group Level/Report Level. 2)When Spotfire migration/deployment is automated( through config import/export commands using batch scripts), the reports tha...
almost 8 years ago in Spotfire / System Administration 4 Future Consideration

Add option to not cache the data from a data function when saving

I frequently use Data Functions to load data from external data sources (e.g. to call RESTful APIs to extract data). The main problem I have with this approach is that the most recent data is saved inside the analysis file. This has 2 knock-on eff...
about 7 years ago in Spotfire / Analytics / Data Functions 0 Future Consideration

Data Canvas UX: Column datatype formatting inside Data Canvas

See attachment The Data Canvas is a great place to manage, wrangle, cleanse, and enrich data. However, the options for formatting column data types are not found within it. You must leave the canvas and go to the Data Panel column handler then s...
about 6 years ago in Spotfire / Data Management 2 Future Consideration

UX: Generally better script management (all scripts)

I know there are different places to script for different functions, but would be good to have a central place to write/manage all scripts in a document. If I am using IronPython with TERR, I have to go in-and-out of two different script handlers ...
about 6 years ago in Spotfire / Scripting 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