What comes out of the two ports on the DBOutputTable component?

Support/help with CloverETL (4.9) and CloverDX (5.0 or newer) implementation problems

pintail
Posts: 33
Joined: Wed Aug 27, 2014 6:58 pm

What comes out of the two ports on the DBOutputTable component?

Postby pintail » Thu Aug 11, 2016 8:30 pm

I'm looking to capture and write out the error messages, and ideally the UID of the record causing the problem.

I tried setting up a meta with ErrCode and ErrText like I saw in the documentation. I can see in debug mode that there is one error record on port 1. But when I open up the debug window both fields are null.

Am I missing a mapping somewhere, or should it be called something else?

1) How can I capture the message?
2) And if possible, can I pass long an ID for the record causing the problem?

thanks in advance for any help

cholastal
Posts: 135
Joined: Tue Sep 01, 2015 1:22 pm

Re: What comes out of the two ports on the DBOutputTable component?

Postby cholastal » Fri Aug 12, 2016 3:13 pm

Hi pintail,

The DBoutputTable is autopropagating the metadata that is on input port to the error output port. There is no need to explicitly setting the error output metadata. So to answer your questions.

    1. The ErrCode and ErrText fields are automatically added to the metadata coming through the input port.
    2. If the input metadata contain some sort of ID you can see it on the output as well (due to autopropagation).

For more information please see the attached graph.

Hope this helps.
Attachments
err_out_dboutput.grf
(3.43 KiB) Downloaded 179 times

---
Lukas Cholasta
CloverCARE Support
CloverDX

Visit us online at http://www.cloverdx.com


cron