figured it out. the ID field needs to be assigned to $original.ID
The "orginal", which is case sensitive, lifts it into a sub-document in the json
which is then ignored by the SET, but you are still able to include it in the WHERE
(I had tried this already, but had typed it as Original, which didn't work, but revisited it once I found sometihng in the help for the SQL SERVER UPDATE Snap
Hello,
The batches is managed by Pipeline Execute.
That complicates things a little bit. You can keep track of processed files in a file, so the next execution will know what number to use. But that will significantly slow down your pipeline 🙂
If there are no concurrent executions of the pipeline, you can simply write down a file with the sequence number used, and set that file as a library expression on the child pipeline itself, so you could easily set the next value:
Example expression in the file writer: "TEST_" + lib.config.sequence + 1 + ".txt"
