Skip to Main Content
Spotfire Ideas Portal
ADD A NEW IDEA

Data Access

Users should only need acess to IL:s - not underlying elements

Give users access to Information links without worrying about or having to give them access/display the underlying elements. "Some of the end users are getting the message in the link decription as per:"Some elements previously added to the Inform...
over 10 years ago in Spotfire / Data Access 0 Future Consideration

Add ability to filter in-db queries during configuration of the source.

We currently initially query the data source for all its content, after setting up a new in-database connection. This can longer than wanted, if the underlying data store contains a large volume of items. So the customer would like to be able to f...
over 10 years ago in Spotfire / Data Access 1 Future Consideration

make connectors list sortable

When accessing data connectors you get a large list that is sorted alphabetical. Since we use TDV a lot it is quite annoying that you have to scroll time and again all the way to the bottom. Would it be possible to create your own sorted list, all...
over 3 years ago in Spotfire / Data Access 2 Future Consideration

Read and write Feather or Apache arrow format

It would be very benefical to be able to read and write Feather or Apache arrow format.
almost 4 years ago in Spotfire / Data Access 0 Future Consideration

Show user id when stored credentials in a data source is used

When a data source is created and saved with stored credentials, the user id is not seen when the data source is being used by end users. End users often use data connections that are based on the source but have no way to tell which user is actua...
almost 8 years ago in Spotfire / Data Access 1 Future Consideration

Spotfire Hive connector, set hive execution engine=spark

Hi, We have a Hadoop big data cluster with Map Reduce as the default Hive execution engine. It is key for us to be able in Spotfire Hive Connector to change the Hive execution engine (set hive.execution.engine=spark). Kind Regards
almost 8 years ago in Spotfire / Data Access 0 Future Consideration

Add Data Table from Data Connection in Library - Should not default to select all tables in connection

Currently, when you add a data table from a Data Connection In A Library, the window opens up and all tables within the connection are selected by default. There is no "deselect all" option so it's the chore of unchecking them one-by-one. I have q...
about 8 years ago in Spotfire / Data Access 0 Future Consideration

Better JSON parsing support

When you get JSON strings and you need to extract a few fields to table format for Spotfire consumption it would be nice having an efficient and easy to use parser to do this out of the box. Something like: JSONGetField( JSONString, ”afieldname” ...
about 8 years ago in Spotfire / Data Access 0 Future Consideration

Import fixed width data tables into Spotfire

Sometimes source data tables are in the format of fixed width, no delimiter being used. Below is an example. Each field has a fixed width of 3 characters, but no delimiter. a def gh abc def g ab de ghi Importing data like this into Spotfire, there...
about 4 years ago in Spotfire / Data Access 2 Future Consideration

Automatically suggest joins in Information Link.

Spotfire should automatically suggest joins, when columns from different tables are added to the Information Link. We want Information Designer to be smart enough to suggest the joins already created, that are required on the Information Link, whe...
over 8 years ago in Spotfire / Data Access / Information Services 0 Future Consideration