Skip Record in Case of Error

Usually, a profile is terminated if an error (like violations of the minimum/maximum constraints or missing mandatory fields) occurs during the mapping. But sometimes you do not want the whole profile to be terminated, for example, if a large number of orders are submitted in a single file. You would only want to skip the order that caused the error but still process all the other orders.

The checkbox Skip record on error can be used to limit errors during the mapping process to the current record. This allows for the subsequent (error-free) orders to be processed.

Error handling can only be activated at the level of a record. As a consequence, the logical unit of a mapping (e.g. an order) must be represented per record. If during the mapping an error occurs in a record, all subsequent phases behave as if the record would not exist.

Note: It is not a termination in the sense of terminating a transaction. Variables that were changed before the error in the record occurred retain the changed values!

If an error occurs, an entry is made in the log files. In addition, it is possible to use variables to collect information about the erroneous/skipped datasets.

• The system variable VAR_SYS_HAS_INVALID_RECORD has the value true if an error has occurred during processing of at least one dataset.

• You can use system variable VAR_SYS_MESSAGE to store relevant information about an erroneous/skipped dataset.

• The contents of variable VAR_SYS_MESSAGE are accumulated in the system variable VAR_SYS_COLLECTED_MSGS.

The variables can, for example, be used in a Response Route to send an email containing information about the erroneous/skipped datasets.