Ideas

Showing 163 of 4839

Support scalar stored procedures

Currently a stored procedure needs to return a table with at least one column in order for Spotfire to create the stored procedure element in Information designer. In Databases like Snowflake, we can have stored procs that only return a scalar val...

over 6 years ago in Spotfire / Data Access / Information Services 1 Future Consideration

3 VOTE

Remove the requirement for a Metadata URL when configuring the OAuth2 client

When configuring an OAuth2 client in the Spotfire server config GUI, the dialogue will not close unless a Metadata URL is entered. It is incorrect to require this since the OAuth 2.0 Authorization Framework (RFC 6749) does not require a metadata U...

about 1 year ago in Spotfire / Information Services 0 Future Consideration

25 VOTE

Better integration and usability features for Admin Tools

The Analyst client, Information Designer, and Administration Tools should be better integrated. There needs to be more productivity featured added. Here are some examples of features that would make authoring and troubleshooting much easier and le...

almost 9 years ago in Spotfire / Data Access / Information Services 1 Future Consideration

1 VOTE

Smart Data Source Optimizer

In many enterprise Spotfire deployments, reports connect to wide tables or views via JDBC or Infolinks, often bringing in 50–200 columns by default—even when only a fraction of these columns are actually used in visualizations, expressions, or scr...

5 months ago in Spotfire / Data Management / Information Services 0 Future Consideration

13 VOTE

Improved support information link sub-queries

The support for sub-queries in information designer is quite limited such that it is e.g. not possible to move prompts inside the sub-query. You can find details in the community and in the support portal.

almost 5 years ago in Spotfire / Information Services 0 Future Consideration

24 VOTE

Subdivide the Information Modeler license - option to limit access to create "data source" in the information designer.

No description provided

about 10 years ago in Spotfire / Information Services 0 Future Consideration

10 VOTE

Allow AS 4.x operator schema to be set by the schema asserted on an input port.

Please refer to Case #02057640 The goal is to have a reusable module that does not need to change itself, but gets its schemas (and the AS operator schema) from context.

over 4 years ago in Spotfire Streaming 0 Future Consideration

10 VOTE

JMS Request/Reply dynamic call along with dynamic custom converter

Feature to configure SB request/reply adapter operator with custom message converter dynamically. Reference To Case ID # 01941085

over 4 years ago in Spotfire Streaming 1 Future Consideration

4 VOTE

Information Designer - Fields Ordered Alphabetically

The fields in information designer would be easier to navigate if there was a visible option to sort alphabetically. Specifically, the fields are non-alphabetized in the data sources.

almost 2 years ago in Spotfire / Information Services / User Experience 0 Future Consideration

12 VOTE

Spotfire Analyst - Add Server and Area in the Information Designer window title

When working with multiple Spotfire Analyst instances, connected to different environments, there is no instant way to know which server the Information Designer is linked to. This is very confusing. Having some more information like in the attach...

over 5 years ago in Spotfire / Information Services 1 Future Consideration

Please enter your email address

FILTER BY CATEGORY