Spotfire Ideas Portal
ADD A NEW IDEA

Custom Expressions

Showing 142

Make a Property's DisplayName usable in custom expressions

When using properties in custom expressions, one can only use the value of the property, not the DisplayName. This would be extremely useful to allow interaction with the DisplayName, particularly when using Expressions in Properties.
7 days ago in Spotfire / Custom Expressions 0 To be Reviewed

GUI interface for OVER expressions

OVER expressions are extremely powerful since they can achieve the same slicing and dicing of data which you can achieve using pivot transformations but in are more interactive way operating on subsets of data tables. At the same time most users w...
2 months ago in Spotfire / Custom Expressions 0 Future Consideration

Allow axis in a visualization to be used as a part of an OVER expression regardless of axis type

Currently, an axis has to be of type Categorical for it to be available in an Custom Expression with OVER() - e.g., [Axis.X] - in a given visualization. However, to add Line and Curves in the same visualization, the axis has to be Continuous. Enab...
3 months ago in Spotfire / Custom Expressions 0 Future Consideration

Enable caching in Expression Function

Data Function has a built-in Allow Caching option to avoid redundant run when input parameters don't change, while Expression Function does not.
8 months ago in Spotfire / Custom Expressions 0 Future Consideration

Add an aggregation method to find the Nth most common value

MostCommon is a pretty useful aggregation method, for example when you have a large set of defective parts across different products and these are defective for different reasons and you want to see the most prominent error say per product. Very e...
9 months ago in Spotfire / Custom Expressions 2 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.
9 months ago in Spotfire / Custom Expressions 2 Future Consideration

Add ability to reference already created values that are defined in a custom expression

Being able to reference already created values that are defined in a custom expression. For example you might use the below custom expression code. I will create an average voltage and standard deviation voltage variables for my typical process. I...
about 1 year ago in Spotfire / Custom Expressions 0 Future Consideration

Allow OVER functions to access multiple aggregations and allow multiple OVERs per Custom Expression

Currently the OVER function is, frankly pretty poorly implemented for anyone wanting to do data analysis that's not time series data. OVER functions should be able to access aggregations in parenthesis. For example, if I wanted to calculate the av...
about 1 year ago in Spotfire / Custom Expressions 0 Future Consideration

calculate over all periods of detail levels

Lets say we have a hierarchy of Year.Month, we want to calculate sum on all the same months (e.g. March) of each year. ParallelPeriod() can only calculate on the same month of previous year.
about 1 year ago in Spotfire / Custom Expressions 0 Future Consideration

should be telling us invalid part of the custom expression visually, not in writting

When an expression written in the custom expression is incorrect or when a function is invalid, an error is displayed with a red exclamation mark which telling us wrong part in writting, not visually. However it is not clear which part of the expr...
over 1 year ago in Spotfire / Custom Expressions 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