Skip to Main Content
Spotfire Ideas Portal
ADD A NEW IDEA

Data Functions

Showing 107 of 4213

Data function parameters 'all data' option when data limited using marking

Data function parameters can be limited using markings but not all the options we are used to with data limiting on visualizations are available. I especially miss a 'if no data is marked use all data' option.
over 3 years ago in Spotfire / Data Functions 1 Future Consideration

Control whether data functions execute when Spotfire initially opens when set to refresh automatically

There is often a need to control the order of running of data functions, or to only run a data function when inputs have changed. Another common use case is to automate these data functions through Automation services. Typically this can be contro...
almost 3 years ago in Spotfire / Data Functions 0 Future Consideration

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

execute multiple Python/TERR data functions in parallel even all of them are from the same Analyst/WP/AS session

We have confirmed with TIBCO support that, currently as designed/implemented how the data function services work, all data function service(Python/TERR) invocations per analysis session are serialized. Also, there is no configuration to force seri...
over 1 year ago in Spotfire / Data Functions 1 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...
over 2 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 7 years ago in Spotfire / Data Functions / Data Management 3 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 1 year 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 1 year 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 1 year ago in Spotfire / Data Functions / User Experience 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 1 year ago in Spotfire / Data Functions / User Experience 0 Future Consideration