Spotfire Ideas Portal
ADD A NEW IDEA

Information Services

Showing 119 of 4351

Add Count and UniqueCount as options to sumarize a column when pivoting data in Information Services

I would like to summarize a data table that I am pulling into Spotfire so I pivoted the data in the Information Link using the Pivot Conditioning Option. The aggregation option for values includes SUM, Avg, Min and Max but no Count or UniqueCount....
over 6 years ago in Spotfire / Information Services 0 Future Consideration

a wizard to convert an SQL-based data table to an infolink and datasource.

we have a nr of data tables based on a SQL query. It would be great if there was a wizard to convert such an SQL-based data table to an infolink and datasource. We develop often 1:1 on the database, and once the analysis is good enough we go throu...
over 6 years ago in Spotfire / Information Services 1 Future Consideration

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

Reuse parameters if the same information link prompts are used by multiple tables

Spotfire should allow reuse of parameters if the same information link prompts are used by multiple tables. I have two or more data tables. All tables use information links with the same prompts (say "fund" and a date range). Becomes confusing and...
over 6 years ago in Spotfire / Data Access / Information Services 0 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

Stop adding new empty row or semicolon in UI when editing fields

Trim ending empty rows and/or semicolon from Connection Initializer, Opens Session Command and Close session command. And, stop automatically adding any new empty row or semicolon in UI when editing any of the fields.
over 6 years ago in Spotfire / Data Access / Information Services 0 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 6 years ago in Spotfire / Data Access / Information Services 0 Future Consideration

Depivot in Information Link

It should be possible to do a depivot in an Information Link.
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
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