Spotfire Ideas Portal
ADD A NEW IDEA

Analytics

Showing 369 of 4418

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 2 years ago in Spotfire / Data Functions / User Experience 0 Future Consideration

Implement the Rprof function

This case is related to TIBCO support case #01791114 which is submitted internally in TIBCO feature requirements database. Whilst applying best practices is obviously something that should be done: It appears that the profiler in R-Studio is broke...
over 5 years ago in Spotfire / TIBCO Enterprise Runtime for R 0 Future Consideration

Enable Setting `NA_character_` in Data Function Parameter

Goal Programmatically set the value of input parameter (String type) in Data Function as NA_character_. Concept Use SetInput() method in DataFunctionInputCollection to set execMode parameter (refer to .png) before executing Data Function. Current ...
over 2 years ago in Spotfire / Data Functions 0 Future Consideration

Sort within a hierarchy

When a hierarchy is used in a bar chart category axis, and then the bars are sorted by value it sorts all the bars by absolute value, without any consideration for the hierarchy. This is not ideal as the reason for setting-up the hierarchy at time...
over 8 years ago in Spotfire / Custom Expressions 2 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...
about 2 years ago in Spotfire / Data Functions 1 Future Consideration

sync updated data function in library to analysis

If data function is added via Transformation, currently one has to perform below steps to sync it from library to analysis if the script in library is updated 1. Navigate to Data Canvas. 2. Select the relevant transformation by clicking on Data a...
about 1 year ago in Spotfire / Data Functions 0 Future Consideration

Create a 'List box' property control with expression within a text area using a table apart from the default table

While working in the Property control dialog, select the property and set 'Set property value through' to 'Expressions'. However, when you attempt to Edit the Expression, only the column names from the default table are visible but not other tables.
over 1 year ago in Spotfire / Custom Expressions 2 Future Consideration

Apply filtering to Regression, DataRelationship and all spotfire analysis tools consistent with table plot way of filter control,

Hi developers, We need to Apply filtering to Regression, DataRelationship, etc and other analysis tools consistent with table plot way of filter control, to add support for Filtering Schemes in these reports and analysis tools This is very impor...
over 5 years ago in Spotfire / Analytics 0 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

Be able to direct an RinR function to a centrally manager R server

Currently if you use local TERR and want to utilize an R script, you can do so using an RinR script. However that script requires a local R engine - you either: Set R engine connection in script – explicit and good for just the script execution M...
over 8 years ago in Spotfire / TIBCO Enterprise Runtime for R 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