Spotfire Ideas Portal
ADD A NEW IDEA

Data Access

Showing 482

Possibility to re-order prompt sequence

To be able to support multiple use-cases with the same template and ultimately same info links it would be required to enable the end user to dynamically re-arrange the prompting sequence. Say the default sequence is prompting for a time range fir...
about 1 year ago in Spotfire / Information Services 0 Future Consideration

Make the Information Designer remember where I last was!

100 times a day. Open Information Designer, navigate complex folder hierarchy, change something...close Information Designer. 2 minutes later, open Information Designer...all the folders are collapsed again, start from scratch navigating the folde...
about 7 years ago in Spotfire / Data Access / Information Services 0 Future Consideration

Multi-factor authentication to connect to Azure database

Trying to connect to Azure SQL DB (using Active Directory - Password), but every time trying to connect to the DB via Spotfire gets the error : ERROR MESSAGE:Cannot connect to '<servername>.database.windows.net'.System.AggregateException: On...
over 2 years ago in Spotfire / Data Access 1 Future Consideration

Support optional prompts in data connections

Information links allow for both optional and mandatory prompts but data connections seem to only support mandatory ones. This means you cannot have a data connection which serves multiple uses cases where one user would like to filter data by a d...
over 2 years ago in Spotfire / Data Access 0 Likely to implement

Analyze data connection and custom queries using Application Profiler

We are using Spotfire Application Profiler to analyze and quality control in bulk all Spotfire dashboards within a certain library folder and this is very powerful and useful. One of the most important topics is to be able to analyze the data conn...
over 2 years ago in Spotfire / Data Access 2 Future Consideration

Spotfire client opens 5 connections to database when using Oracle data connectors, and hold them till closing the client

When we use a data connection to retrieve data from an Oracle database, the Spotfire client opens 5 connections to the database with each usage. Those connections remain open even after you close the template using File > Close. The only way to...
almost 3 years ago in Spotfire / Data Access 1 Future Consideration

Spotfire Connector to Power BI XMLA EndPoints

Our organization uses a lot of Spotfire but there are other BI Tools in use, particularly Power BI. Our Spotfire teams of late have been getting asked to connect to what are referred to as "XMLA Endpoints". Power BI workspaces use an "XMLA endpoin...
over 1 year ago in Spotfire / Data Access 0 Future Consideration

Improve cube functionality in Spotfire

There is a lot of potential for improvements with using cubes in Spotfire. Here are some functions that I would like to see: Ability to use on-demand with cubes Cube dimensions to allow data types other than String (like Dates) Ability to "Limit d...
over 4 years ago in Spotfire / Data Access 1 Future Consideration

Open session commands (pre post statements) for data connections

We have many data sources that implement row level security using features such as Oracle’s VPD. This relies on the ability for Spotfire to provide the end user identity whenever running SQL on the database - which is easily achieved using the Ope...
over 5 years ago in Spotfire / Data Access 6 Future Consideration

option to make sure Analyst always use bundled ADO.NET driver for TDV

Please add option to make sure Analyst always use bundled ADO.NET driver for TDV when loading data via TDV connector, in order to avoid unintended / unsupported version of driver being used. Currently if ADO.NET driver for TDV is installed to the ...
3 months ago in Spotfire / Data Access 0 To be Reviewed
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