You can view a report in Microsoft Excel format that contains the errors that occurred during a message run. You can, for example, use this to inform the sender of data on the errors.

You can create an error report:
  • Automatically: To do so, on the message header, select 'Yes' in the 'Create history report' field. The report is created when the message run is finished.
  • Manually: To do so, on the Connectivity studio Integration operations workspace, on the History errors tab or History tab, select a record, and click Create history report.
The report is stored in the folder as defined in the Business integration parameters, in the History report path field. This is a folder in the file share as defined in the Windows share field.
To view a history report, open the Azure file share or Windows folder, as defined in the Windows share field on the Business integration parameters.
You can find the report based on the message name. The name of the history report is composed in this way: Message [message name]_[number sequence].


Notes

By default, the history report shows the fields in the sequence as defined for a document record. You can re-organize the fields on the report. To do so, on the Document page, on the Action Pane, on the Design tab, click History report setup.

The History report setup page shows, for each document record, the record fields. To re-organize the fields on the report, in the 'Use in history report' field, select the desired option for each field:
  • No: The field is not shown on the report.
  • Identifier: The field is used as identification of the error message. On the report, it is shown before the error message field. 
  • Detail: The field is shown after the error message field on the error report.
Note that on the message history lines, the Identifier field is shown. This field is filled with the values of the fields that you have marked as Identifier. This makes it easier to find the record that caused the error.
On the History report setup, you can mark several fields as identifier. Best practice is to only mark one or a few fields as identifier.

Provide feedback