Spotfire Ideas Portal
ADD A NEW IDEA

Data Functions

Showing 114

Passing calendar dates from Spotfire tables into Matlab data-structures via a Data Function without having to recalculate the dates

Currently calendar dates in Spotfire tabular data are received through a Data Function into Matlab as dates counted from 1/1/1960 rather than from the standard calendar starting point. This requires performing in the Matlab Data Function a convers...
over 8 years ago in Spotfire / Analytics / Data Functions 0 Future Consideration

Data Functions to pass Spotfire data in Tables into Matlab objects of type "Table", "Array" or "Matrix" instead of "Structure"

Currently Spotfire tabular data is received through a Data Function into a "Structure" object (a datastructure where each column is recorded and accessed as a separate field). This is a structure much harder to manipulate in Matlab than a Matlab "...
over 8 years ago in Spotfire / Analytics / Data Functions 0 Future Consideration

Enable "Replace Data Function" if a new .sfd is available

Say I have a data function (e.g. TERR) embedded within a Spotfire file. An updated copy of that data function becomes available as an .sfd file (maybe I sent a copy of the Spotfire dxp to a colleage, or to a different VM environment, and an improv...
over 8 years ago in Spotfire / Data Functions / Data Management 0 Future Consideration

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 ...
almost 9 years ago in Spotfire / Analytics / Data Functions 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