KrushanthanR Member since 2010 9 posts
Virtusa (pvt) Ltd
Posted: 2 years ago
Last activity: 2 years 9 months ago

What is the alternate solution for using force commit when saving data in to an external DB which is highly normalized

Hi All,

We are using an external Database as source of truth which is highly normalized. In a single flow, we have a requirement to save the data in average 25-20 tables. Since this DB is highly normalized, we are using Write-Now option to force commit the changes in order to handle the foreign key violations.

But, in case of an error in the middle of the transaction we don't have a way to rollback as we don't use the Pega OOTB commit. This is causing data integrity issues in exception scenarios.

Please let me know if you have encountered this issue and resolved it in your projects.


Low-Code App Development Data Integration
Moderation Team has archived post
Share this page LinkedIn