Change Data Capture With SnapLogic
I frequently get asked by customers - does SnapLogic support Change Data Capture (CDC)? My response usually is - what does CDC mean to you? What are you looking to do?
While there are a few organiz...
Forum Discussion
Concept is good but how can we make sure to update timestamp only when bottom path is successful?
@Piyush, I usually do something similar to this: I add an Error output to the bottom flow (Load SFDC) and add an Exit Snap to that Error output. As well, I break the top flow to link to the Union Snap that is linked to the Exit Snap. I also add notification logic (a reusable, nested Pipeline) to the Error output, but that’s not required to address your question.
The Exit snap will not produce a document if there is not an error, so the top flow will continue through the Union to the Update Timestamp without interference. Otherwise, if there is an error on the Load SFDC snap, the “notification logic” will send notification and the Exit snap will halt the pipeline before the Union can proceed to the Update Timestamp Snap…
Replying to my own post… You need to test… It seems like I had one case where I needed to add a Sort at the end of the Union to make sure all processing prior to the Union completed to allow the Exit to work before moving forward, but I can’t think or find that case right now.
