Skip to Main Content
Spotfire Ideas Portal
ADD A NEW IDEA

Ideas

Add support for converting/handling SQL Server DATETIMEOFFSET fields

In the MS world, developers are frequently using the DATETIMEOFFSET type to specify a point in time at a given time zone offset. The type is common in SQL Server and C# code (probably more). Data like this ends up in SQL Server data sources. TDV d...
almost 3 years ago in Spotfire Data Virtualization / data sources 0 Likely to implement

Add a Favourites folder and Recent Locations option to Information Designer

THis would save a lot of time. The Information Designer doesn’t even remember where you were last, and open at that location. You have to constantly navigate from the root folder. Adding Favourites and Recent Locations would be a great help. Also,...
over 8 years ago in Spotfire / Data Access / Information Services 2 Future Consideration

Allow the view Definitions to be published along with the view

Users are not able to see the view definitions of the views that they connect to through the Data Virtualization tool. View definitions are required for QA teams and other users to validate that the view is bringing back the correct information.
over 7 years ago in Spotfire Data Virtualization / data movement 0 Future Consideration

Redshift connector should be available in the web clients' flyout

I want to be able to author connections to Redshift using from Spotfire Business Author.
over 4 years ago in Spotfire / Data Access 0 Planning to implement

Pivot / Un-Pivot with in-database connections

When working with in-database connections it would be useful if it was possible to push pivot and un-pivot operations down to the database instead of requiring that data is in Spotfire memory when performing these operations.
over 8 years ago in Spotfire / Data Access 0 Future Consideration

Add global parameter that can be applied to custom queries

Add a global parameter that can be applied to custom queries query parameters so the parameter can be defined prior to executing the queries. Allow the use of these params in custom queries so the query can be run with settings of imported data, a...
11 months ago in Spotfire / Data Access 0 Future Consideration

Set the dimension to be used as a measure in the Essbase Connector

Following this idea: https://ideas.tibco.com/ideas/TS-I-5554 It would be useful to be able to set the dimension to be used a measure, even though there is already account dimension found by Spotfire. in short, being able to define (already implem...
over 7 years ago in Spotfire / Data Access 0 Future Consideration

Oracle Number(0) values are represented as Currency in Spotfirer 10.10

When we load data from Oracle into Spotfire, the integer values (represented as Number(0) in Oracle) are translated into Currency columns in Spotfire data tables! The mapping between Oracle Number(0) and .Net data type is not correct and leads to ...
over 4 years ago in Spotfire / Data Access 1 Unlikely to implement

Detailed lineage in Business Directory

Right now the Business Directory presents a summary of the table level lineage, i.e. what data source the data originates from. We need to add support for the full detail lineage at the table level as well as detailed column level lineage like we ...
over 8 years ago in Spotfire Data Virtualization / data catalog / metadata 0 Future Consideration

Provide self-tuning capabilities for data sources

Have the server be able to scan a data source and learn capabilties for the data source so that the user does not need to edit or customize the capabilities files themselves. If a function doesn't exist allow the developer to add it without updati...
over 8 years ago in Spotfire Data Virtualization 0 Future Consideration