Spotfire Ideas Portal
ADD A NEW IDEA

web services

Showing 20 of 4770

Enable custom JSON structures for published web services

Developers need to have the ability to explicitly define the shape of JSON objects they want to expose via a REST service. Currently, users have no way of explicitly controlling how TDV will make the JSON object appear.
almost 8 years ago in Spotfire Data Virtualization / web services 2 Future Consideration

Wizard-guided configuration for REST data source

The REST adapter supports a wide variety of functionality and options, but all these options appear on a single page, and there is no guidance on the order of steps needed to make it work. For example, it can be very confusing to figure out exactl...
almost 8 years ago in Spotfire Data Virtualization / web services 1 Future Consideration

Support Navigation Properties in OData

Navigation properties allow to represent semantical links between objects in OData. A link that is technically established as the translation of a foreign key - primary key relation could semantically mean different things. E.g. in banking the acc...
almost 5 years ago in Spotfire Data Virtualization / web services 0 To be Reviewed

Allow contract first for REST/OData

Contract first design of REST/Odata APIs is common in many enterprises. As SOAP contract first is already supported, Contract first in REST would allow us to receive Openapi 3.0 specifications and link the data virtualization to this exact contrac...
about 5 years ago in Spotfire Data Virtualization / web services 0 To be Reviewed

Add the ability to include TDV descriptions in the OpenAPI specification

It is possible to generate an OpenAPI specification from the ODATA CSDL, however CSDL doesn't include the descriptions of the entities and attributes of the published objects. It would be useful if we could include the descriptions as this will al...
almost 5 years ago in Spotfire Data Virtualization / web services 0 To be Reviewed

Skip NULL fields in JSON responses (REST Data Service)

When exposing a table/view using REST Data Services, the JSON responses include fields with a NULL value explicitly. In some cases for tables sparsely populated this can add a lot of overhead (tons of NULL fields). This is being the case reported...
over 7 years ago in Spotfire Data Virtualization / web services 0 Future Consideration

Add A Button to Check and Uncheck All Column in TDV Web UI - Flow - Column Node / Object

In TDV Web UI, if a user creates a flow that contains a "Column" object/node, then at the bottom of the display, there is a list of columns available in the table being operated along with checkboxes for each column name. When a user works usin...
7 months ago in Spotfire Data Virtualization / web services 0 Future Consideration

Able to set default settings for webservices JSON operation property and parameters and maintain after re-publish for REST

For REST webservices operation in TDV. We can select setting for our webservice in Web Services => REST => Operations => Property and Parameters Example: Default Property value are like ==== HTTP Method : GET ... Input Message ...
over 2 years ago in Spotfire Data Virtualization / web services 0 Future Consideration

Provide a way for a Published TDV web service's Schema to use Input arguments as-is

Provide a way for a Published TDV web service's Schema to use Input arguments as-is, instead of pre-pending them with the Operation name
almost 3 years ago in Spotfire Data Virtualization / web services 0 Planning to implement

Build a DV Mobile App and allow publishing the resources as Web Services and Data Services to external users

It will provide more flexibility for our customers to extend the availability of the application and it's resources to their external users with the swipe of a finger
almost 8 years ago in Spotfire Data Virtualization / web 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