Spotfire Ideas Portal
ADD A NEW IDEA

Analytics

Showing 355

Produce warning when changing engine type in data function

Users can change the engine type in a data function without resetting all of the code, inputs, and outputs, which is fantastic. However it is maybe a little too easy to change this. I found just an accidental touch of the mouse scrolling switched...
about 8 years ago in Spotfire / Analytics / Data Functions 0 Future Consideration

Add expression function to convert Temperature

This is one of those simple things that you'd think would be in the tool already, but just isn't. Here's an example of how it's implemented in Excel. I would use the exact same approach. https://www.extendoffice.com/documents/excel/1254-excel-co...
about 8 years ago in Spotfire / Custom Expressions 0 Future Consideration

Bi directional integration with Clarity

Today Clarity can be used in front of Spotfire for Data cleaning (and also could be used to import more easily xml or json files). Could be really great to integrate Clarity from our new source view and see rules to clean data from Sprofire and m...
about 8 years ago in Spotfire / Custom Expressions 0 Future Consideration

Preserve row index order even after join operation

As per current Spotfire design, when doing the join, there's no row order guarantee afterwards, and it may change depending on algorithm used internally. It seems we used different algorithms for different data sizes because of memory / cpu tradeo...
over 8 years ago in Spotfire / Custom Expressions 0 Future Consideration

Enable caching in Expression Function

Data Function has a built-in Allow Caching option to avoid redundant run when input parameters don't change, while Expression Function does not.
9 months ago in Spotfire / Custom Expressions 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