I’m not sure I understand this question; but will try to answer.
If the output from your pipeline just before the email sender is 2 separate documents due to the way your pipeline is set up; the email sender creates a table row for each document (i.e. a table with 2 rows). If your output was 30 documents, the table would have 30 rows.
However, by adding the aggregate snap before the email sender, it reduces all the individual documents into a single document - therefore the email sender will only create a table with one row.
Thanks for the comprehensive answer!
Hi Pranil,
Are you trying to pass the eror reason, error and resolutions as parameters to the error pipeline from the parent?
The document that caused the error will be passed directly to the child pipeline and need not be passed as parameters, the passed document contains the error reason, error resolution, etc, which you can then parse and write to an excel sheet in the error pipeline itself.
Thanks,
Chaitanya.
Hi Chaitanya,
Thanks for the reply. In error pipeline, how to refer the error reason variables/parameters? in error pipeline, i am using Mapper and not able to find the snap error/ error variables. Please can you give me an example for reference.
Hi Pranil,
you can reference to the details you need by using the $ in the mapper in the error pipeline like below screeshot:
Below is a sample pipeline:
errpipe_2019_11_25.slp (2.2 KB) errchild_2019_11_25.slp (5.2 KB)
Hi Chaitanya,
Thanks for the example. it works straight away.
For reference, from where we can get this list of error variables, which u have listed 4 of them.
Thanks again.
Hi Pranil,
You can see them in the preview data of the parent pipeline when u validate it. The 4 error variables i have listed are the standard for any error document.
Hi Chaitanya,
Thanks for the Information and it is very helpful.
