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
I just had a similar experience myself.
I wanted to use a newer version of TERR with Spotfire and downloaded a Spotfire patch that contains the TERR update. I tried applying the patch to Spotfire Server, but got a database error. I didn't want to investigate the error right away since it'll hold me up from what I want to do on TERR and Spotfire. As a result, I downloaded and installed the latest version of TERR separately. It turns out that for Spotfire to use the new version of TERR I installed separately, I have to replace the "engine" folder of the TERR module that came with Spotfire with the one in the new TERR install. I feel the whole process should be easier.
I also wish for an option to not have to go to Spotfire Server to apply a patch, although I do see the reason for doing this through a centralized admin server.
Sometimes it is easier to upgrade the TERR engine locally before upgrading Spotfire for enterprises that takes time to upgrade. Instead of going to IT for an upgrade, it will be easier for end users to simply have another TERR installation and point it directly from Client - They use data connection to SQL for data
There are other use cases where providing flexibility to upgrade TERR would make sense especially for enterprises who take time to upgrade
Why would you want to do that?