Spotfire Ideas Portal
ADD A NEW IDEA

Data Access

Showing 481

Allow editing of MDX queries through information designer

There are many ways to optmize or improve the load time of information links -- change drivers, modify SQL, change cach, pivot, etc. There are zero options for optimizing connections to cubes. Allowing MDX queries to be edited would be helpful or ...
over 8 years ago in Spotfire / Data Access / Information Services 1 Future Consideration

Ability to set time zone for Information Services Data Sources/JDBC Connections

When accessing data via an Information Link, the JDBC driver on the TIBCO Spotfire Server is used to access data. JDBC sets it's client machine time zone as the default session time zone to use so when using a JDBC connection, for some of the data...
about 2 years ago in Spotfire / Information Services 0 Future Consideration

Connector parameters for selecting database in multi-tenant environments

A setup might be something like this. Let's say there is CustomerAnalytics schema. Under that main schema there is a database for each individual customer (customer_a, customer_b, etc.). Each database has a same structure (tables, views, etc.). Ru...
about 4 years ago in Spotfire / Data Access 2 Future Consideration

Optional Prompt in Information Links

I would like for a prompt to be smart enough to known when there is only one option available for a user and to automatically select and use that value instead of prompting the user. We have data that is secured by company and power users that can...
over 6 years ago in Spotfire / Information Services 0 Future Consideration

Teradata connector to support OAuth/OIDC

When connecting to Teradata using the Spotfire connector, there should be an option to use OpenID Connect / OAuth 2.0 for authentication and authorization. It is expected to have a SSO experience when using the same identity provider for Teradata ...
about 2 years ago in Spotfire / Data Access 0 Likely to implement

Ability to Hide or Disable the Data Sources tab in Information Designer

Information Designer users can easily see data sources that have been created by other users using the Data Sources tab in Information Designer. It is often unintentional that teams expose their data sources in this way. It enables and encourages ...
over 6 years ago in Spotfire / Information Services 4 Future Consideration

Make it possible for the admin to remove "Create Data Source" from Information Designer yet keep the ability to add elements and joins.

At our company we only want the admins to create data sources. We store them in a shared but secure folder. All users work from that folder to create the elements that everyone uses. When user's create their own data source is confuses others and ...
over 6 years ago in Spotfire / Information Services 2 Future Consideration

Multiple values as prompt type in Input Parameters to Stored Procedure element

Spotfire Information Services should support multiple values as prompt type in Input Parameters to Stored Procedure element.
over 6 years ago in Spotfire / Data Access / Information Services 0 Future Consideration

Ability to change column name in an information link

I am having a problem renaming a column in an information link to be effective in a Spotfire analysis.To be more precise, i created an information link in which there is a join between 2 tables. This join results in adding 2 columns to my pincipal...
over 6 years ago in Spotfire / Data Access / Information Services 0 Future Consideration

Amazon Redshift connector OAuth support

The Amazon Redshift connector should support Open ID Connect / OAuth2 as authentication / authorization option. If I'm logged into Spotfire using OIDC with a shared identity provider I expect SSO to Amazon Redshift.
about 2 years ago in Spotfire / Data Access 0 Planning to implement
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