Spotfire Ideas Portal
ADD A NEW IDEA

Data Management

Showing 293

Change Default Number of Decimals on Imported Data

Currently when you import real data into Spotfire it always truncates the results at 2 decimal places, would like the ability to change the default import to whatever number would best fit the data. If it has to be a hard number than change it fro...
about 7 years ago in Spotfire / Data Management 4 Future Consideration

Add Trust option for custom queries for Spotfire Desktop.

Th Custom Queries feature allows users to execute a database query when connecting to a database but before ingesting data into Spotfire, which works effectively to limit data processing times for a large data table. Custom queries must be execute...
over 1 year ago in Spotfire / Data Management 0 Future Consideration

Check data (during load) for quality and changes in column values

Users appreciate Spotfire’s ability to match column name changes during data reloading. This ideas proposes the ability for Spotfire to check data (during load) for quality and changes in column values (especially when metadata changes or when dat...
7 months ago in Spotfire / Data Management 0 Future Consideration

bring back the "reload with prompt" button in spotfire X

please bring back the "reload with promped" button for linked data tables in the data table properties of spotfire X like it was implemented in Spotfire 7.xx. This option should only be available for linked data tables. It would be good to have a ...
over 5 years ago in Spotfire / Data Management 0 Future Consideration

Add export capability for data prep/ data wrangling in data canvas

In Spotfire data canvas, users is able to view the data modeling diagram as well as transformations for data wrangling and preparation in the data canvas. But it's really hard for users to see the data transformation processes taken for data table...
about 5 years ago in Spotfire / Data Management 3 Future Consideration

Data Canvas: Export/Import of ”node configurations” (transformation collections) to be reused in other dxp files.

It would be very productive if it was possible to export/import parts of the configurations (collections of actions) from the data canvas – to be (re)used in other dxp files. Despite that it is possible to exchange data sources in a dxp, which som...
over 4 years ago in Spotfire / Data Management 1 Future Consideration

Pre-defined DateTime ranges for loading data (on-demand)

We need to report on data that is filtered on many columns and special DateTime intervals. Information Links are very large so we need to set filters as part of the query that imports data into Spotfire so that only the rows needed by the report a...
about 5 years ago in Spotfire / Data Management 0 Future Consideration

Better Logic / Control over Column Name Changes

Hello, I've recently had a support case (Case#2463638) about unwanted column name changes when using the "add rows" feature in combining data sets. In discussions around that case, we documented some inconsistencies around column name changes that...
4 months ago in Spotfire / Data Management 0 Future Consideration

Table relations and cycles

When you get to a certain level of complexity in your DXP file, you often hit problems with cyclic dependencies between data tables. It would be extremely helpful to be shown where the cycles exist when you are trying to add new relations. Further...
12 months ago in Spotfire / Data Management 0 Future Consideration

In Column Properties > Sort Order, add "sort based on ..."

Add a fourth radio option. If selected we can use an expression to set the sort order based on other column(s) in the same table. e.g. my table has categoryName, categorySequence I would select the new option, and sort expression would simply be [...
almost 6 years ago in Spotfire / Data Management 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