Spotfire Ideas Portal
ADD A NEW IDEA

My ideas

Showing 4317 of 4317

Force "always new data vs. stored data" selection on save

When working with Spotfire *.dxp file cooperatively, the collaboration is very often hampered by the fact, that Spotfire tends to save *.dxp files as “linked”=”Always new data” by default. That happens in particular when: Spotfire is used when st...
about 5 years ago in Spotfire / Collaboration / Data Management 1 Future Consideration

Provide and match default input and output handlers for Data Functions

WHAT: Currently a Data Function author much specify the inputs and outputs for the Data Function, and that information is included in the Data Function definition. However, when a data function is added to a DXP (whether from a .dfd file or the Li...
over 8 years ago in Spotfire / Analytics / Data Functions 2 Future Consideration

Synchronize Data Functions with copy in library

Once a data function is loaded into a DXP from a file, it is impossible to then synchronize/link that data function with a known identical copy in the library. Would be useful to be able to re-establish this link, once it is broken. (Each copy has...
over 8 years ago in Spotfire / Analytics / Data Functions 0 Future Consideration

Add additional slicing possibilities for line graphs

It would be very helpful in some cases to have additional ways to split data in line graphs. Here are a couple examples: A "Shade By" option that works in conjunction with the "Color By" option. So you could have a categorical column selected for ...
over 1 year ago in Spotfire / Visualization 0 Future Consideration

Customization of Line and Curves Labels

Example: For a vertical line, in Lines and Curves (Scatter Plot), have the option to change the line label to horizontal text, compared to vertical text, to make the information easier to read. This would also give the ability to add more infor...
about 5 years ago in Spotfire / Visualization 0 Future Consideration

Duplicate Data Function definition

Sometimes, I want to register a data function with a script that is already present in the analysis but slightly different parameters. For this, I have to register a new data function and select all the input/output parameters again. "Copy" in the...
about 5 years ago in Spotfire / Data Functions / Scripting 0 Future Consideration

Share a single analysis without having to share a library folder

I need to share a single analysis with my team. It is cumbersome to have to create a library folder, move the analysis into it, and then share the folder. I want to be able select an analysis, click share and add people with who I want to share th...
over 1 year ago in Spotfire / Library 0 Future Consideration

Add callback function to the JavaScript API to trigger when filters are changed in an analysis

Currently there is a callback function that can be registered for Marking changes, but this isn't possible with the Filter. This is useful to catch changes in Spotfire filters in a wrapping web application. Right now the only way to do this is a m...
about 5 years ago in Spotfire / API 2 Future Consideration

Loading Selected Columns from large files

Currently, if you have a very large file with several worksheets and columns within those worksheets Spotfire must read every column in that file even if you're only using a handful of columns. This makes download and refresh times very long compa...
about 5 years ago in Spotfire / Data Management 2 Future Consideration

Size setting of marker layer setting in map chart

Even if you do not use terrain CRS, it would be easier to use if you could apply the "Keep marker size absolute relative to geography" in the size settings of the marker layer settings in the map chart.
over 1 year ago in Spotfire / Maps 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