Skip to Main Content
Spotfire Ideas Portal
ADD A NEW IDEA

Data Access

Allow descriptions to be added to prompt filters

It would be great, if when defining prompt filters in the Information Link, if you could add text providing additional information to the users at each prompt. This could be used to describe the data point, and the impact of the choices being ma...
almost 7 years ago in Spotfire / Data Access / Information Services 1 Future Consideration

More details in action log for Information Links

The new(ish) action logging for data connections is excellent - we can easily see from a single record what type of database was used, the specific database, how long the query took and how much data was returned. Extracting similar data for Infor...
almost 7 years ago in Spotfire / Data Access / Information Services / System Administration 0 Future Consideration

use parameter as identifier in Information link SQL

From time to time, we receive requests from our customers that they want to load data from database where table name is dynamic, e.g. on demand load data from different tablenames all of them have the same column structure. Unfortunately currently...
over 2 years ago in Spotfire / Data Access / Information Services 0 Future Consideration

On demand load for data from library

We have lots of measurement data in a database and basically all dxps use on demand load of data. However, for some special measurements, the data can only be made available in the library. However, as the amount of data is quite big, is usually m...
almost 8 years ago in Spotfire / Data Access 0 Future Consideration

Spotfire should support have a native connection template for accessing OLAP on hadoop cubes like Kyvos, atScale or Kylin.

As OLAP on hadoop is a hot topic at the moment, the support by spotfire is lacking some native connectors. Kyvos for example, can only be connected via the MS SSAS connector and atScale is only availabe via SQL connectors. A better support and int...
over 9 years ago in Spotfire / Data Access 0 Future Consideration

Active Directory - Connector / Extension

A connector/extension to be able to fetch data from Active Directory (Users, Groups, Computers, Printers and so on) would be a great feature. Could TIBCO integrate this natively in the Spotfire Analyst? Thank you.
almost 8 years ago in Spotfire / Data Access 4 Future Consideration

Facilitate easier changing of data types in the Information Designer

TIBCO needs to change the Information Designer and make it easier to make mass changes to data types. Currently, this has to be done one by one, column by column. There are functions that allow quicker changes through transformations or the data p...
over 9 years ago in Spotfire / Data Access / Information Services 4 Future Consideration

TIBCO Spotfire Connector for Hortonworks- Specify YARN queue for Hive queries

Currently there is no way to specify the yarn queue that should be used to run Hive queries. So all queries from Spotfire are run in the default queue. Hortonworks ODBC driver enables this in HTTP Options by specifying it in Custom HTTP Headers......
over 9 years ago in Spotfire / Data Access 1 Future Consideration

Improve metadata loading performance in the Google BigQuery connector

When a user has access to many projects with many tables in Google BigQuery it may take a long time to list all the tables when configuring a connection in Spotfire. This is somewhat mitigated by turning of the setting Connectors > Google BigQu...
over 2 years ago in Spotfire / Data Access 0 Future Consideration

Identifying Datatypes importing .csv file.

If columns in .csv file have empty cells, they are identified as "String" automatically when the first 101 cells are empty (or null), and any other value e.g a real value after that cell Spotfire will still consider the data type "String" while it...
over 9 years ago in Spotfire / Data Access 1 Future Consideration