Skip to Main Content
Spotfire Ideas Portal
Status Implemented
Product Spotfire
Categories Library
Created by Guest
Created on Feb 9, 2020
Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit SPF-I-310 Library Version Control.

Template versioning (analysis history) Merged

It would be great if Spotfire gives us the ability to track the history of any template natively. By this I mean the ability to know when a template was created and by which version of Spotfire and when it was updated and by which version. It would also be great if the logged-in user name is recorded in history to know which user did what chaznge... 

Another great customization would be the ability to provide us with an API to add extra details to the history (e.g. add our own custom module version number or any other custom piece of information).

This means that there should be a way to look at the history of any template ...

Implemented in 12.0
    Jul 12, 2022


    I'm happy to announce that library version history has been implemented in Spotfire 12.0 LTS.

    You can now browse saved analysis versions and go back to any previously saved version (either to restore the version, or to save a previous version as a new file) in the Spotfire library.

    Version history reduces the need to redo work if mistakes are made, facilitates collaboration and troubleshooting, and provides change traceability.

    Version history is available, not only for analysis files, but for all the visible Spotfire library items, like data sources, data functions, color schemes, SBDF files, mods, automation service jobs, etc.

    This means that, if you are working in teams, it is easier to work together on different parts of the same analysis, tracking changes and resolving conflicts for each separate part on its own, if you choose to work this way.

    For more information, see the What's new in Spotfire 12.0 LTS and the release notes and product documentation.


  • Admin
    Miguel Díez
    Oct 14, 2020

    Thanks for the use case information in our chat, Samer !

  • Guest
    Feb 10, 2020



    I may used the wrong expression "Template versioning" ... I agree this is confusing. 

    A better title would be "Template (Analysis) History" where we track within the analysis document (dxp file)  the following info:

    1. creation date + Spotfire version + owner

    2. update date + Spotfire version + owner

    3. custom module version (via API)


    A generic API may be needed to add extra info similar to the API GenerateDataHistoryCore available in CustomDataSource ... 

    Having all this info embedded in the template makes it easier to track when it was created and by which SF version and who updated it.


    I hope this is a better description.



  • Admin
    Tobias Lehtipalo
    Feb 9, 2020

    Samer, by template do you mean a Spotfire Analysis file (dxp file) stored in the library? Is your request different from what is described here: ?