Spotfire Ideas Portal
ADD A NEW IDEA

All ideas

Showing 4327 of 4327

When filtering with != or <>, do not remove null/empty values unless it was specified.

When the condition for != or <> is filtered on, it should not filter out null/empty values unless it was specified in the condition. For example, if there is a field called "Number" with a list of numbers 1,2,3,4,5,6,,7,8 (null between 6 and...
about 3 hours ago in Spotfire / Filters 0 To be Reviewed

Make Remember Personalized View option work with Custom Scripting and Properties

Dear Team, Our customer is utilizing IronPython scripts to add custom properties within their Spotfire analyses. This customization appears to affect the behavior of the "Personalized View" option, resulting in unexpected synchronization issues be...
4 days ago in Spotfire / User Experience 0 To be Reviewed

Parameterize column selection of information link to reduce DB load and RAM usage

Hello everyone, to provide standardized information links to Spotfire users it would be very useful to have a option to parameterize the column selection of a information link. Goal is to keep database load and RAM usage under control by loading o...
13 days ago in Spotfire / Data Access 2 Future Consideration

Provide a setting to control automatic column addition in joins.

Currently, for every join, columns that were added at a later moment to one of the sub/right tables are automatically joined into all joins where this table is used. In most cases this is not desired. Proposed feature should work by either turning...
about 2 months ago in Spotfire / Data Management 0 Future Consideration

Email Hyperlink

Other BI platforms allow for email by clicking on an icon. It would be useful to have the same in Spotfire so that when we are given an example of a dashboard to reverse engineer, we can add that functionality. The lack of it gives the appearance ...
4 days ago in Spotfire / Actions 0 To be Reviewed

Visualization performance for complex configurations with large datasets

I need to visualize individual data points across different type of charts for analyzing chip production data. In some cases Spotfire may use excessive amount of memory and take some time to render visualizations. It is important for us to see all...
5 days ago in Spotfire / Visualization 0 Future Consideration
629 VOTE

Microsoft 365 Sharepoint Online Files access

Our company has migrated to Office 365 SharePoint. Neither the Spotfire OData connector or Infomatix SharePoint Connector can connect to Office 365 SharePoint. They only work with on-premise implementations. We created workarounds to import ShareP...
over 7 years ago in Spotfire / Data Access 53 Future Consideration

Implement resource pool concept in automation scheduled jobs

We are in in need that we must have a resource pool concept in automation services too. So we can redirect some specific automation schedule jobs to run via dedicated server. It is kind of a huge set back that till now we do no have this feature i...
about 2 months ago in Spotfire / Automation Services 0 Future Consideration

Preconfigure the server connections for the Spotfire Mobile apps

As a Spotfire Administrator I would like to pre-configure the Server connection URL that are available in the app when the user installs it, to avoid that each user has to manually type it in.
12 days ago in Spotfire / Mobile 0 Future Consideration

Add the ability to change the x-axis for Control Charts in WebStatistica

WebStatistica does not allow us to assign a different parameter to the x-axis on SPC charts. Typically users would want to see something like a lot number on the x-axis or even a date so that they would be able to look at the chart and know what t...
7 days ago in Spotfire Statistica 0 To be Reviewed
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