Skip to Main Content
Spotfire Ideas Portal
ADD A NEW IDEA

Data Functions

Showing 103

Add auto-retry on failed data function call in case of 401/500 error from statsvc

Problem: If Statistics services returns 401 or 500 error (that happens often enough for our users), current behavior of Webplayer (10.3) is to just fail. Usually it is enough to do manual retry, or do analysis F5 refresh but that is inconvenient f...
about 4 years ago in Spotfire / Data Functions 0 Future Consideration

Add "Limit data using expression" functionality to data function input data

When specifying input data for a data function, I am missing the "Limit data using expression" function. The limit by filtering and/or marking is there - but not the expression? This would really help limit the number of records sent to R for proc...
over 8 years ago in Spotfire / Data Functions / Data Management 3 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 2 years ago in Spotfire / Data Functions / User Experience 0 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 3 years ago in Spotfire / Data Functions 0 Future Consideration

sync updated data function in library to analysis

If data function is added via Transformation, currently one has to perform below steps to sync it from library to analysis if the script in library is updated 1. Navigate to Data Canvas. 2. Select the relevant transformation by clicking on Data a...
10 months ago in Spotfire / Data Functions 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 8 years ago in Spotfire / Analytics / Data Functions 3 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 5 years ago in Spotfire / Analytics / Data Functions 0 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 2 years ago in Spotfire / Data Functions / User Experience 0 Future Consideration

Drop Down input control for f(x) flyout

Drop down for pre-determined values in input values. If document property related, must be able to store options in SFD file.
over 2 years ago in Spotfire / Data Functions / User Experience 0 Future Consideration

Tagging/grouping of data functions in f(x) browse

Be able to group and/or tag data functions into collapsible groups. Would be nice to be able to control the icons and have language indicated automatically. This would make it easier to access and find data functions.
over 2 years ago in Spotfire / Data Functions / User Experience 0 Future Consideration