Spotfire Ideas Portal
ADD A NEW IDEA

My ideas: Data Functions

Showing 102

Enable asynchronous (parallel) execution of two TERR data functions when not using TSSS (local execution)

In advanced analytics often we're running various TERR data functions simultaneously to analyze our data and sometimes it is desirable to execute data functions locally (e.g. if data transfer times to and from the TSSS would exceed computation tim...
about 6 years ago in Spotfire / Analytics / Data Functions 0 Future Consideration

Surface Python warnings without having to enable debugging

I think it would be very helpful for developing data functions if we could surface warnings without involving the debugging feature. Sometimes for instance there is a call to an API and that call may fail; one way of designing the code would be to...
about 1 year ago in Spotfire / Data Functions 0 Future Consideration

TERR Graphical limitations

One of the requests that I receive most from users who are R and Python programmers, is the request that within Spotfire they could create graphics using the open source language packages. I know that currently the TERR engine does not provide gra...
over 3 years ago in Spotfire / Data Functions 0 Future Consideration

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...
over 2 years ago in Spotfire / Data Functions 0 Future Consideration

Ability to specify plots as outputs from data functions

WHAT: Ability to specify plots as outputs from data functions (in additions to binary objects, tables, columns and single values). Somehow specify when creating the data function at least minimal info to create plot (e.g., Visualization type, vari...
about 8 years ago in Spotfire / Analytics / 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 7 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 th...
almost 5 years ago in Spotfire / Data Functions / Scripting 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...
over 6 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...
about 8 years ago in Spotfire / Analytics / Data Functions 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...
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