https://answers.axonivy.com/questions/3828/ivy-business-data-store-rollback-in-case-of-problem-transaction-management<p>Hello IvyTeam,</p> <p>We are using the Ivy.repo() API for storing our data. Let's say we want to save a list of objects and if there is a problem by saving one of them, we should rollback what has been done for the previous ones.</p> <p>Is there a kind of transaction management with the Ivy.repo() API? Can we work like in one "transaction" for having the advantage of such a rollback function?</p> <p>Or should we implement it by our own, like going back to previous objects versions? Do you know how to achieve that?</p> <p>Thanks a lot in advance Emmanuel</p>enTue, 28 May 2019 03:56:42 -0400https://answers.axonivy.com/questions/3828/ivy-business-data-store-rollback-in-case-of-problem-transaction-management/3829<p>Hi there</p> <p>Business data uses an <strong>optimistic locking</strong> approach: so it gives you many possibilities for save update/write/merge scenarios <a href="https://developer.axonivy.com/doc/latest/DesignerGuideHtml/ivy.datamodeling.html#ivy-businessdata-concept">https://developer.axonivy.com/doc/latest/DesignerGuideHtml/ivy.datamodeling.html#ivy-businessdata-concept</a></p> <p>This is why we can provide rock solid persistence mechanisms reflected by multitudes of write methods (save, update, overwrite): <a href="https://developer.axonivy.com/doc/latest/PublicAPI/ch/ivyteam/ivy/business/data/store/BusinessDataRepository.html">https://developer.axonivy.com/doc/latest/PublicAPI/ch/ivyteam/ivy/business/data/store/BusinessDataRepository.html</a></p> <p><img alt="alt text" src="https://answers.axonivy.com/upfiles/businessDataRepo_update.png"></p> <p>So I guess you are looking for the update() method which provides the richest capabilities to react on persistence failures.</p> <p>If you have the rollback of non-atomar write operations in mind, then it is a very different case. To support this would be a paradigm break for optimistic locking. As optimistic locking is designed to get rid of all the problems of classical tx based write scenarios. </p> <p>So basically if you have list of objects that belongs together for being in a consistent state, it should also be shared in the same businessData object. But maybe we clarify this better with a concrete data model. Feel free to share it :-)</p>Reguel WermelingerTue, 28 May 2019 03:56:42 -0400https://answers.axonivy.com/questions/3828/ivy-business-data-store-rollback-in-case-of-problem-transaction-management/3829