Spotfire Ideas Portal
ADD A NEW IDEA

Spotfire

Showing 4067

Change default encoding to Unicode (UTF8) when replacing data table in Spotfire using Ironpython script

refer to the support ticket - 01862613 We have code in place which replaces data table based on dynamic parameter passing for multi clustered sql data. This works perfectly fine in english. But since because the encoding cannot be done before load...
over 4 years ago in Spotfire / Data Access 3 Future Consideration

Missing add data table transparency in an existing Data Connection

Spotfire doesn't allow user to set import method when extending a SQL server data connection after 1 data table already included in connection. I have a dashboard with MS SQL server data connection embedded in analysis. As of now there is only 1 t...
over 4 years ago in Spotfire 0 Future Consideration

Spotfire Server - Avoid false positive when new server configuration is uploaded to the database

When a new Spotfire Server configuration is uploaded to the database, a WARNING message shows up under Nodes & Services -> Notifications, informing that the Server 'XXXX' must be restarted to use the latest configuration (see attached scree...
over 4 years ago in Spotfire / System Administration 0 Likely to implement

Schedule time zone picker should have standard timezones listed.

Automation and Scheduled updates time zone picker has to be reworked to support timezones not only by city names, but by standard timezone name and/or UTC offset. Problem: Imagine the following use-case. You need to set schedule according to Bosto...
about 4 years ago in Spotfire / Scheduled Updates 0 Likely to implement

Allow configuring user rights for information designer and data connections with identical right sets

Independet from whether data is accessed using information links or data connections a company would like to be able to control the user rights in an identical way. In our case we would like to be able to define three analyst levels where „setting...
almost 4 years ago in Spotfire / Data Access / Information Services 0 Future Consideration

Display Barcodes from alphanumeric strings

The requirement is to be able to display a barcode in a tabular visualization from an alphanumeric string. Other applications can do this, using techniques that I think requires specific fonts to be used that render as barcodes. It's currently pos...
3 months ago in Spotfire / User Experience / Visualization 3 Future Consideration

In-DXP display of file location for current .dxp

When opening a .dxp in an Analyst client, there's currently no way for users to see its file path via the GUI. This creates a quandary when saving the file under the same filename - e.g., unintentional overwrite. Programmatically, this can be done...
5 months ago in Spotfire / User Experience 0 Future Consideration

Allow SQL queries to select columns based on Spotfire input

Certain data lake solutions are optimized for column access (e.g. Google's BigQuery). Trying to access a column in BQ using Spotfire fails because a string literal is the only option for the variable. If a second variable option was available that...
over 2 years ago in Spotfire / Data Access 0 Future Consideration

Spotfire Server - Make the upgradetool.bat keep previous service parameters

I would expect from an upgrade tool where an input on the previous installation folder is required, to copy over to the new Spotfire Server the settings from the previous installation. This is especially relevant for the JvmMs and JvmMx settings, ...
over 4 years ago in Spotfire / Installation 0 Future Consideration

Cross Table: Show both Sum and Average in Totals

The Cross Table needs to be able to show the Total Sum as well as the Monthly Averge (average of resulting sums) in the Totals Section.
over 4 years ago in Spotfire / Visualization 1 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