Spotfire Ideas Portal
ADD A NEW IDEA

Data Functions

Showing 109 of 4339

Categorize data functions

i find the new data function capabilities in Spotfire really useful and the ability to pin data functions to an easily accessible data function panel is very handy. However the long list of functions looks a bit intimidating. It would make it much...
about 3 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...
about 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...
over 8 years ago in Spotfire / Analytics / Data Functions 0 Future Consideration

Keep old output columns when adding new output columns in data function

Say we have a data function that has column A as output. When the script is altered and a new column B is added as output, then an additional column A is added along with the new column B. However, as calculated columns etc. might depend on the ol...
almost 7 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...
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

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

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

Python Data Function - Add Row Number

Display row numbers for Python scripts in the Edit Script workspace. This is present in R data functions but I don't see it when writing a Python function. This is useful for debugging code with the referenced line numbers.
over 5 years ago in Spotfire / Data Functions / Scripting 0 Future Consideration

model version by ModelOps in Spotfire

now you can link a Modelops model from Spotfire by Spotfire UI, setting server, project, scoring flow and target environment. It would be very useful to have also the version, or, better, choose if a data function is linked to the published versio...
about 2 years 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