Spotfire Ideas Portal
ADD A NEW IDEA

Data Access

Showing 473

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.
about 6 years ago in Spotfire / Data Access / Information Services 0 Future Consideration

Disable default runtime-query-validation in Information Services

TIBCO should disable runtime-query-validation for Information Services as the default configuration. The Information Modeler and the Report Developer wants the system to be configured for performance and visibility for issues, when querying data ...
about 6 years ago in Spotfire / Data Access / Information Services 0 Future Consideration

Post-process a data table after it is loaded

I have the need to post-process a data table after it is loaded, automatically without clicking a button. My scenario is : - spotfire file is loaded and the data is retrieved from various databases - once loaded I need to post-process data as do...
about 6 years ago in Spotfire / Data Access 1 Future Consideration

Spotfire Query Banding

There is a query banding option if we try to connect to Teradata using ODBC connection. But for other connections like JDBC or any other ODBC (except Teradata) there's no option for query banding. Query bands can be used to improve performance. It...
about 6 years ago in Spotfire / Data Access 1 Will not implement

Ability to union table components

The information designer allows you to union two data sources, say two SQL views, but you can only do this if the views are the same size, which is a huge limitation. For example, I have two tables -- Header 1 and Header 2. One as 100 columns and ...
about 6 years ago in Spotfire / Information Services 1 Future Consideration

Change Data Type Transformation holds change for when the column is already that type

I am loading data tables from excel, where sometimes the columns are real, and sometimes they are integers. I change the data type so that they are always real with a transformation. If the Q01 column is real when I add the transformation, it does...
over 6 years ago in Spotfire / Data Access 0 Future Consideration

Monitoring Data Source connections (Spotfire Analyst) for Failure

Monitoring of data source connections in Spotfire Analyst is critical to the functioning of associated Spotfire reports. If one/few connections are not working due to database outage, then it will be useful to immediately notify End users that rep...
over 6 years ago in Spotfire / Data Access 2 Future Consideration

Scheduled refresh of connector data into a file cache

You should be able to configure in-memory data connections you have stored in the Library to fetch data according to a schedule. Data would be stored in a shared cache on the Spotfire server. Your analysis files that are using the cached data conn...
over 6 years ago in Spotfire / Data Access 0 Future Consideration

Use Summary Duration for PI Connector for Interpolated instead of # of Points

Currently with the PI connector, you have to select number of points when using interpolated. This means you have to calculate how many data points are between a specific time range and you have to change number of points it every time the time ra...
over 6 years ago in Spotfire / Data Access 0 Future Consideration

Multiple marking to get data into detailed data on demand visualization which uses stored procedure as source

when you are working with the huge data sets. we usually built two visualizations in a page. one as base visualization and other as detailed visualization liked to base visualization. base visualization is data connected to information link and th...
over 6 years ago in Spotfire / 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