Skip to Main Content
Spotfire Ideas Portal
ADD A NEW IDEA

Data Functions

Showing 107

Show required packages in f(x) flyout

At beginning of flyout, so user does not have to figure out by error and author does not need to enter in description as free text.
over 3 years ago in Spotfire / Data Functions / User Experience 0 Future Consideration

Use (In-memory) Visualizations as input to Data Functions

WHAT: Enable the data currently displayed in a visualization to be sent to (any) Data Function, either automatically (when the visualization changes) or not. WHY: Much easier development of predictive analytic applications & easier ad hoc usa...
over 9 years ago in Spotfire / Analytics / Data Functions 3 Future Consideration

Automatic Retries When Statistics Servers Are Too Busy to Respond to Status Requests

When the Spotfire Analyst client or a Spotfire Web Player sends a job request to a Stats server, it polls the server every 10 seconds. If it doesn't hear back from it in 10 seconds, it kills the job. We think that it would be better behavior if it...
about 4 years ago in Spotfire / Data Functions 0 Future Consideration

Spotfire Data Functions need to support native 'String List' type as inputs or outputs

Spotfire's Data Funcitons are among the top differentiators from its competitor tools and I use them often to create very valuable and sophisticated user work-flows that takes a complex process and makes it seem trivial. In creating a specific wor...
over 6 years ago in Spotfire / Analytics / Data Functions 0 Future Consideration

Limit input options on f(x) flyout

Limit options for input params so user cannot select data in an unintended way. For instance, Column selection may not want to allow column expression.
over 3 years ago in Spotfire / Data Functions / User Experience 0 Future Consideration

Allow for dropdowns or fixed options in data function flyout

When configuring or registering a data function, I'd like to be able to enforce fixed choices for those input parameters. When running the function in a dashboard with document properties you are able to set options, however when you are running f...
about 1 year ago in Spotfire / Data Functions 1 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 2 years ago in Spotfire / Data Functions 0 Future Consideration

Default value for optional parameters in data functions

When an optional parameter is used, I have to test in the data function whether the parameter is set using is.null() and assign it a default value. e.g. if(is.null(optPar)) {optPar = "something} because otherwise the code usually fails because you...
over 6 years ago in Spotfire / Data Functions / Scripting 0 Future Consideration

Drag a Data Function from one DXP to another

WHAT: Enable the user to drag a Data Function from one DXP to another. Prompt to match inputs (doc properties, tables, columns, etc.) if don't match WHY: Make it easier to share and reuse data functions. Additional comments: 1. If implement idea o...
over 9 years ago in Spotfire / Analytics / Data Functions 1 Future Consideration

f(x) flyout package installation directly

When a required package is determined to be missing, allow install directly from input param flyout
over 3 years ago in Spotfire / Data Functions / User Experience 0 Future Consideration