Spotfire Ideas Portal
ADD A NEW IDEA

Data Functions

Showing 103

Supported Team Studio Data Function

Currently unsupported as a Community Extension
over 2 years ago in Spotfire / Data Functions 1 Future Consideration

Data function management UI consistency

Which UI to go to in order to do different things with data functions? Not clear/obvious currently. Many frustrations with these UI's. How is it clear that "Run" also registers? And then this isn't where I go afterwards to edit the data function
over 2 years ago in Spotfire / Data Functions / User Experience 0 Future Consideration

Manage Model objects between data functions

One data function used to train a model, another used to predict with new data. Need easy way to retain model between data functions. Using the "pickle" package works but is but cumbersome. Perhaps "Analytics Models" could be used.
over 2 years ago in Spotfire / Data Functions 1 Future Consideration

Keep f(x) flyout items up-to-date with library

When a data function has been deleted from library, it does not always reflect in the flyout (possibly because a client reload is needed?). Data functions are also not updated with the latest version in the library, nor is existing version number ...
over 2 years ago in Spotfire / Data Functions / User Experience 0 Future Consideration

Hidden Tables should not show in data functions

Unchecking “show in user interface” for a data table still allows the data table to show in the DF flyout
over 2 years ago in Spotfire / Data Functions / User Experience 0 Future Consideration

Data Function output column names should be Display Name

When outputting a column from a data function, the column name is not the display name but rather the parameter name
over 2 years ago in Spotfire / Data Functions 0 Future Consideration

Automatic Data Function package install

Admin and/or Analyst option to automatically install required packages if they are missing at runtime of a data function
over 2 years ago in Spotfire / Data Functions 0 Future Consideration

Segment input params in f(x) flyout

Allow groupings of input params; perhaps horiz line between groups
over 2 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.
over 2 years ago in Spotfire / Data Functions / User Experience 0 Future Consideration

Show required packages in f(x) flyout

At beginning of flyout, so user does not have to figure out by error and author does not need to enter in description as free text.
over 2 years ago in Spotfire / Data Functions / User Experience 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