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
reviving this
a Quickfix would be to have an option to disable TDV pre-processing before presenting data through a REST service -
i.e. the ability to send [rawdata] FROM a TDV REST endpoint, the same way we can send [rawdata] TO a REST endpoint.
As it is, TDV makes assumption on the structure of data it's returning, and tries to add ",: and escape characters in what it believes to be value-pairs and strings.
When a TDV REST service returns JSON with custom structure, this obviosuly breaks the output.
An addition to this is that we need to have the ability to build JSON objects and pass them back to REST webservices. There is no easy way to do this apart from passing the [rawdata] parameter to a REST call. We should have some built in UI options for creating these JSON structures... It gets a bit gnarly trying to append JSON to a VARCHAR variable in a sql procedure.