Spotfire Ideas Portal
ADD A NEW IDEA

Data Functions

Showing 114

Enable Setting `NA_character_` in Data Function Parameter

Goal Programmatically set the value of input parameter (String type) in Data Function as NA_character_. Concept Use SetInput() method in DataFunctionInputCollection to set execMode parameter (refer to .png) before executing Data Function. Current ...
over 2 years ago in Spotfire / Data Functions 0 Future Consideration

Webplayer need a function to get current date based on user's location regardless of webplayer server's timezone

As of now webplayer user gets data time functions return current date and time based on the server time where the webplayer is hosted. This causes issue if the users and webplayer server are in different time zone. For example today() function cal...
about 3 years ago in Spotfire / Data Functions 0 Future Consideration

ODBC Netezza - more SQL function please

Hello If we create a direct query with ODBC netezza, we are really poor on function (Calculated colomns or Personnalized expression). Why can't we use SQL ANSI function working on Netezza ? Example : CURRENT_DATE is not working. A user can't creat...
over 4 years ago in Spotfire / Data Functions 1 Future Consideration

Using Open source Octave as an alternative to Matlab

I been working with a programing tool called Octave. The language is almost identical to basic Matlab. The discriminating difference is that Octave is open source and free. Octave offers similar performance efficiencies to Matlab.
over 4 years ago in Spotfire / Data Functions 0 Future Consideration

Embedding Data Functions

We use Data Functions from our server library to quickly add features to new DXP files. The issue we are having is once you add a data function to a new DXP file it keeps the server path. If someone make a change to the function and then saves, it...
over 8 years ago in Spotfire / Analytics / Data Functions 0 Future Consideration

Allow users to unhook embedded data function from Spotfire library

If a user has a dxp file containing an embedded TERR data function that is synchronized with the Spotfire library, the path to the library is visible in the Data Function Properties dialog. If the user makes a change to the local copy and saves wi...
almost 9 years ago in Spotfire / Analytics / Data Functions 0 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...
about 9 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...
about 9 years ago in Spotfire / Analytics / Data Functions 0 Future Consideration

Data Functions: provide a built-in option for returning a static graph directly from a call via TSSS or TERR to an R function that generates a graph

Data Functions: provide a built-in option for returning a static graph directly from a call via TSSS or TERR to an R function that generates a graph.
about 9 years ago in Spotfire / Analytics / Data Functions 0 Future Consideration

Data function save as

Add a [Save as..] button to make a copy of the data function along with all the mapped parameters. When it comes to developing data functions or creating different versions of different data function, it takes too long too map all parameters for t...
over 1 year ago in Spotfire / 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