Spotfire Ideas Portal
I'd like to be able to use API to export and import library items (objects, folders, dxp, etc) from the library to local drive or to server drive. At the moment having to use the configtool from within a custom tool is very awkward and not efficient or elegant. The library API's should be able to perform this task (analogous to the configtool or from within the Library administrator).
| Implemented in | 14.0 |
Hi,
I'm happy to announce that we have a new Spotfire Library REST API (v2) for better Library asset management in Spotfire 14.0 LTS.
For more details on this release, see the What's new in 14.0 page.
For a complete description of all new features, changes in functionality and how customers can upgrade/migrate to this version, see release notes and product documentation.
Thanks!!!
Hi @Guest ,
I'm reviewing some ideas. This was previously merged with the Library REST API, that was released in Spotfire 14.0.
Anyhow, I've unmerged this idea because now I'm noted that your case requires not only management of individual library items, but export&import managing all item dependencies, or a group of items (t.ex. within a folder). Is that right?
Also, I'd like to confirm if your preferred method would be using REST API. We believe that is the most useful case since with the REST API so you can do the operation from an external server, not necessarily within the Spotfire environment. If not, why?
Thanks
Miguel
Hi Jens,
In the first instance I would prefer to use the .NET API. In this way you have a direct connection to the Spotfire (library).
Just like the configtool is awkward to use from within a tool in the client, the web service also brings its own problems, especially over vpn, slow connections etc. For instance trying to retrieve a list of (all) the folders or (all) library items in the library via the web service, limits the amount of data that can be retrieved; whereas with the .NET API you can retrieve all items in the library without as problem. Also, it's not always straighforward when you want to capture errors that might occur during an import or export process via the web service.
I prefer, to start off with, the plain client api implementation instead of the batch file of the configtool or the web service.
Kind regards, Anton.
Are you referring to the .NET API, the web service API or both? If both, would you prefer one of them?