Skip to Main Content
Spotfire Ideas Portal
ADD A NEW IDEA

Data Access

Showing 479 of 4298

Spotfire should support any ODBC DSN in-database

Spotfire should support any ODBC driver and DSN in-database so that we could connect to any ODBC compliant data source using connectors and in-database live query analytics. It's also important to have all connection string options available when ...
about 6 years ago in Spotfire / Data Access 0 Future Consideration

Kerberos Delegation supported with OpenID Connect authentication setup

In a hybrid setup with multiple legacy data sources on-prem and new data sources in the cloud, Spotfire should be able to request and "impersonate" the user with Kerberos. So the frontend supports OpenID Connect for authentication and the backend ...
over 3 years ago in Spotfire / Data Access 0 Future Consideration

Official support to connect to MongoDB via JDBC

Although you can use a JDBC driver on the Spotfire server and connect to MongoDB via Info Links, this is not yet officially supported as I was told. Consequently I do not get support as I'm having weird issues. Since Mongo is more and more used, o...
about 7 years ago in Spotfire / Data Access 6 Future Consideration

Support scalar stored procedures

Currently a stored procedure needs to return a table with at least one column in order for Spotfire to create the stored procedure element in Information designer. In Databases like Snowflake, we can have stored procs that only return a scalar val...
almost 5 years ago in Spotfire / Data Access / Information Services 1 Future Consideration

Connectors Load Type Visibility

Show whether in memory or in database when creating connection as you often don't realise it defaults to in-database. Change default to in-memory or allow it to be configurable in options or administration manager.
about 2 years ago in Spotfire / Data Access 0 Future Consideration

Choose the default data type when importing Excel files

It would be useful to have a default data type setting when importing Excel files. This would prevent the user from having to select a certain type for each column if they wanted them all to be the same. For example, if a user wants all of the col...
about 2 years ago in Spotfire / Data Access 0 Future Consideration

Limit concurrent loading datatables in custom data source and Information Link

A prevention function is needed to prevent some users from occupying DB sessions or resources by loading large amounts of data. AS-IS : Not available TO-BE : Provides a setting function to limit the number of concurrent loading datatables in cu...
about 1 year ago in Spotfire / Data Access / Information Services 0 Future Consideration

Shorter loading time for custom data sources

When loading a file with a custom data source, the loading time becomes longer in proportion to the number of columns. So, they need to requires shortening of loading time. AS-IS : Repeat processing as many columns TO-BE : - Repetitive proces...
about 1 year ago in Spotfire / Data Access 0 Future Consideration

kdb+ Connectivity

It would be very useful to have a Data Connector for kdb+. Connecting directly via ODBC is inconvenient when several tables cause prompts for logins, for example.
almost 4 years ago in Spotfire / Data Access 1 Future Consideration

Need ability to retrieve the list of AD groups and spotfire groups a user belongs to in spotfire as a new column.

This request is raised as an extension to the case id : 01598902. Although %Current_user% and %current_group% attributes are possible to be retrieved in the information link (personalized information link) in the where clause. Currently there is n...
over 6 years ago in Spotfire / Data Access 0 Future Consideration