Spotfire Ideas Portal
ADD A NEW IDEA

Data Functions

Showing 103

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.
almost 4 years ago in Spotfire / Data Functions 1 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...
almost 6 years ago in Spotfire / Data Functions / Scripting 0 Future Consideration

Data function does not have option to enable/disable prompting

Unlike tables from data sources, the data tables from data functions have their 'Prompt for new settings before loading' check box disabled. This means that we have no real control on when a data function prompts users for new settigns! It would b...
over 2 years ago in Spotfire / API / Data Functions 0 Future Consideration

Custom data functions should have same UI components (menu items) as custom data sources

The recommendation from TIBCO support is to switch using custom data sources to custom data functions. Support provided the following link to show how this can be done: https://community.tibco.com/wiki/wrap-data-source-inside-data-function The mai...
over 3 years ago in Spotfire / Data Functions 0 Future Consideration

LongInteger is missing in Register Data Functions menu

In case I have a column define as LongInteger data type, then I create a new function and insert an input parameter as type "Column". We noticed the following: 1. LongInteger is missing in the allowed data type list. 2. I'm not able to select the ...
almost 8 years ago in Spotfire / Data Functions / Data Management 0 Future Consideration

Data Function New vs Insert

Merge register new with insert as it can be confusing to users. The process of registering a data function and then clicking run to embed it isn't as intuitive as it could be for new users. Could we remove this step somehow?
over 2 years ago in Spotfire / Data Functions / User Experience 0 Future Consideration

AutoSynch Library TERR Data Function Parameters, not just scripts

I'm able to force an auto-sync of a library function upon opening a Spotfire template. This is very useful for distributed templates among many users, as incremental changes in the function will be automatically pushed to every user. However, the ...
over 6 years ago in Spotfire / Data Functions / Scripting 2 Future Consideration

Possibility to enable (and restrict) Spotfire Analyst Python and TERR packages to use a customer-defined repository of packages.

Representing requests from multiple of our customers, we strongly advocate for a solution to requests for the following additional capability (ies) in Spotfire: As a visual data scientist, i want to make sure to use only Python packages in my data...
11 months ago in Spotfire / Data Functions 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...
over 3 years ago in Spotfire / Data Functions 0 Future Consideration

Add option to not cache the data from a data function when saving

I frequently use Data Functions to load data from external data sources (e.g. to call RESTful APIs to extract data). The main problem I have with this approach is that the most recent data is saved inside the analysis file. This has 2 knock-on eff...
about 7 years ago in Spotfire / Analytics / 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