Skip to Main Content
Spotfire Ideas Portal
ADD A NEW IDEA

Data Functions

Segment input params in f(x) flyout

Allow groupings of input params; perhaps horiz line between groups
about 4 years ago in Spotfire / Data Functions / User Experience 0 Future Consideration

Clone inputs from one data function to another

Clone inputs from existing data function in analysis so params do not need to be re-entered. DFs can have lots (15 or more) of inputs.
about 4 years ago in Spotfire / Data Functions / User Experience 0 Future Consideration

Improved Column Input selection for Data Functions

When making columns to pass to a data function dynamic, it can be difficult for users to set the columns to use as it requires expressions, especially if multiple properties are involved. Allow selection of columns from multiple properties without...
about 4 years ago in Spotfire / Data Functions 0 Future Consideration

Percentile() - allow different calculation types (as in TERR) for calculated columns

TERR allows 3 discrete and 6 continuos calculation variants for quantile() which ends in different results. It can be controlled by optional 3rd parameter. Default value is 7. However expression language used for calculated columns only supports t...
over 4 years ago in Spotfire / Data Functions 0 Future Consideration

Script/Code display options and font size settings for custom expression editor and TERR data function editor

In IDEs such as RStudio and Eclipse, there are global options for users to set how the code editors should look (e.g. font size, tab width, auto intent etc.). Having such an option for the custom expression and data function editor in Spotfire mak...
over 9 years ago in Spotfire / Data Functions / Scripting 1 Future Consideration

Add ISOYear to BinByDateTime

Usefulness: Using the current BinByDateTime expression, users can create a continuous X-axis in visualisations for Year>>Month, Year>>Quarter, etc. This isn't possible for Year>>Week, as for instance January 3rd of 2021 belongs t...
almost 5 years ago in Spotfire / Data Functions 1 Future Consideration

Allow a TERR data function to output columns straight into a visualisation

Currently, TERR can output columns only into a fully loaded data table. If we wish our TERR column result to respond to filters or markings*, we must import not just the filtered table but also at least one column of the potentially massive origin...
over 9 years ago in Spotfire / Analytics / Data Functions 0 Future Consideration

Provide a data function to interact with geo analytics REST APIs

When my data are related to addresses, routes, itineraries the only way to geocode or reverse geocode is to log into the geoanalytics web interface and do that manually. Currently one can use TERR, however the issue is that for the Web Player you ...
over 10 years ago in Spotfire / Data Functions / Visualization 0 Future Consideration

Data functions should consider visual properties

Trellis by panel operation on data function execution results shows incorrect data in all split panels.This is an enhancement to support Data functions to any visual properties
over 10 years ago in Spotfire / Analytics / Custom Expressions / Data Functions 0 Future Consideration

Exclude Data Functions from executing during Scheduled Updates cache

*Goal:* As a administrator I want the option to exclude particular data functions from execution during Scheduled Updates since the data is personalized and the cached data is invalid and it will be executed again when the end user opens the repor...
over 10 years ago in Spotfire / Analytics / Custom Expressions / Data Functions 0 Future Consideration