Current situation:

  • FirstSpirit allows the versioning of data set content in data sources:
    • when changing content in a data set, a new version is created for the edited data set (based on timestamps) within the BerkeleyDB
    • when deleting a data set, the old version is still available within the version history
  • when manipulating (DELETING or CHANGING) a data set containing a foreign-key relationship with other data sets (1:n; m:n; 1:1), the relationships will not be restored when switching to a former version via the following functions (see screenshot enclosed):
    • restoring deleted objects ("Gelöschte Elemente wiederherstellen")
    • restoring an old version within the version history ("Wiederherstellen einer alten Revision in der Versionshistorie")



  • data corruption

Feature request:

  • when restoring a versioned data set referencing other data set resources via a 1:1, 1:n, m:n relationship, there is no option in the GUI available, whether to restore the dependent relationships as well or not
  • currently, the assumption that all relationships are reconstructed as well, is wrong! Just the CURRENT data set without any relationship is restored! This leads to data corruption!
Tags (2)
1 Comment
Crownpeak employee
Crownpeak employee

Hello Holger

thank you for your idea to improve FirstSpirit. It is important for us to learn from the experiences of our customers and partners. For this reason we appreciate feedback and any suggestion.

We have evaluated the issue once again, but have no plans for a realisation in the near future. Therefore, we cannot consider your feature request at this time. Since FirstSpirit 5.2R1811 you will be informed that references possibly can be lost.

You can find more details about our feature selection process in our Features Policy.

Best regards