Spotfire Ideas Portal
ADD A NEW IDEA

Data Functions

Showing 111

Produce warning when changing engine type in data function

Users can change the engine type in a data function without resetting all of the code, inputs, and outputs, which is fantastic. However it is maybe a little too easy to change this. I found just an accidental touch of the mouse scrolling switched ...
almost 9 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...
almost 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 ...
almost 9 years ago in Spotfire / Data Functions / Maps 0 Future Consideration

Provide and match default input and output handlers for Data Functions

WHAT: Currently a Data Function author much specify the inputs and outputs for the Data Function, and that information is included in the Data Function definition. However, when a data function is added to a DXP (whether from a .dfd file or the Li...
almost 9 years ago in Spotfire / Analytics / Data Functions 2 Future Consideration

Synchronize Data Functions with copy in library

Once a data function is loaded into a DXP from a file, it is impossible to then synchronize/link that data function with a known identical copy in the library. Would be useful to be able to re-establish this link, once it is broken. (Each copy has...
almost 9 years ago in Spotfire / Analytics / Data Functions 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...
almost 9 years ago in Spotfire / Analytics / Data Functions 1 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...
almost 9 years ago in Spotfire / Analytics / 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...
almost 9 years ago in Spotfire / Analytics / Data Functions 3 Future Consideration

Data Functions: provide a built-in option for returning a static graph directly from a call via TSSS or TERR to an R function that generates a graph

Data Functions: provide a built-in option for returning a static graph directly from a call via TSSS or TERR to an R function that generates a graph.
about 9 years ago in Spotfire / Analytics / Data Functions 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
about 9 years ago in Spotfire / Analytics / Custom Expressions / 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