Line breaking during CSV Parser
Hey Everyone,
Here’s an example of what I’m having issues with, since the contents that are inserted into the NOTES column have multiple line breaks. The data I’m receiving is via SFTP and wanted t...
Forum Discussion
Sorry, I’m still having trouble understanding what the issue is.
Are you saying that every time the child pipeline runs, it’s overwriting the same file? Then why not just change the file name so that it’s unique per execution? There are many ways to do that, such as appending pipe.startTime or pipe.ruuid to the name.
Also, even if the file is being overwritten every time, why can’t you just look at the latest version written?
You can also just validate the child pipeline by itself to test it by setting the pipeline parameters to default values that test the functionality you want to test.
PipelineExecute will invoke the child pipeline for every document.
As @christwr mentioned, the default behavior in PipeExec is to spawn a child for every input document. It sounds like you want the opposite behavior, to start a single child that processes all documents received by the PipeExec. You can switch to that behavior by selecting the Reuse executions to process documents option.
Thank you very much.
