Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Krushanthan Ragunathan (KrushanthanR)
ACC3 International Inc
Lead System Architect
ACC3 International Inc
US
KrushanthanR Member since 2010 10 posts
ACC3 International Inc
Posted: Nov 20, 2017
Last activity: Dec 5, 2017
Posted: 20 Nov 2017 10:03 EST
Last activity: 5 Dec 2017 10:54 EST
Closed

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.

Thanks

To see attachments, please log in.
Low-Code App Development
Data Integration

  • Anoop Korah
Posted: 7 years ago
Posted: 21 Nov 2017 3:36 EST
Ujjwal Kumar Shukla (UjjwalShukla_GCS)
PEGA
Senior Manager, Technical Support
Pegasystems Inc.
IN

Hi Krushanthan,

Write Now option should be avoided if possible for the same issue that you are facing now.

However if you have to do it then before every write get the deferredOPS queries and save it in a property.

Later reconstruct the query using those for rollback and then fire it using connect sql or other means.

Regards,
Ujjwal

To see attachments, please log in.
Posted: 6 years ago
Posted: 5 Dec 2017 10:54 EST
Krushanthan Ragunathan (KrushanthanR)
ACC3 International Inc
Lead System Architect
ACC3 International Inc
US

I have found an article related to this issue, this is yet to be tested. I'll keep this post updated.

https://collaborate.pega.com/question/pega-86-post-upgrade-existing-sql-query-results-pycommiterror

 

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice