DSXchange

Without an output link from the container to the upsert flow, they will be treated as two different flows and will be executed simultaneously. And a sequential cannot have a input link and output link (unless it is a reject link). So this approach wont work. Have the second flow (upsert) in a second...

Set the value for all the environmental variables to $PROJDEF. If you run the job then the value for APT_CONFIG_FILE is the same as the project default. Even if the job is moved to a new environment, you can just run the job, and the value defaults to the project default. And at run time you can als...

That option is like a double negative and quite confusing. If you don't check the box then your sequence will be restartable as in, run from the previously failed activity. If you check the box, then the activity will run every time you run the sequence, irrespective of whether it ran successfully o...

The .bad and .log files are created in the scratch disk that is defined in configuration file used to run the job.

Hmmm. As always best possible solution. Make sure you check "Preserve Sort Order" box in the transformer and "Duplicate To Retain" property to "Last" in Remove Duplicates stage.

Use an aggregator stage to get the count of the records for each group of keys (3 in your case). In a transformer have a variable count the input records. You will have to initiate it to 1 for every new group of key values. Constraint the output link to pass the record only when the counter equals t...