1. To-Increase Dynamics 365 for Finance & Operations
  2. Connectivity studio
  3. Operation
  4. Monitor inbound web service history

Monitor message history

You can review and analyze the history of message runs that have run with errors. You can investigate these errors and take the appropriate actions to solve the errors. If the errors are solved, you can re-run the message run.

To monitor the message history, use the Connectivity studio integration operations workspace.

 


Application Consultant Application Consultant Start Start View message run history View message run history You can review and analyze the history of message runs. Procedure 1. Click Connectivity studio Integration operations. 2. The History errors tab shows the message run history records with errors. On the History errors tab, in the list, find and select the desired message run. Note: You can view the full message run history on the History tab. 3. Click History. Note: You can also open the message run history from several other places. For example, the Connectivity studio Integration design workspace and the Message page. 4. Close the page. Notes If no records are processed, also no errors are reported. Possibly caused by:The document record range: A document range limits the records that are processed. So, if no records are processed unexpectedly, verify the document record range.Message mapping conditions and field conditions: Conditions limit the records that are processed. So, if no records are processed unexpectedly, check if conditions are defined for the message on the record mapping or field mapping. Investigate the error Investigate the error View message run record history View message run record history For each message run, the processed records with errors are shown. For each shown record, you can view the record details. If required, you can change the values to be set. Procedure 1. Click Connectivity studio Integration operations. 2. On the History errors tab, in the list, find and select the desired message run. 3. Click History. 4. Expand the Lines section. 5. In the left grid, find and select the desired record. Note: For each record, 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 fields as identifier. Best practice is to only mark one or a few fields as identifier. 6. In the fields list, find and select the desired record. 7. Click Edit. 8. In the Value to field, type the desired value. 9. Close the page. Show Infolog for run Show Infolog for run For each message run with errors, you can open the Infolog and read the related error messages. Procedure 1. Click Connectivity studio Integration operations. 2. On the History errors tab, in the list, find and select the desired message run. 3. Click Show Infolog. View original message run history View original message run history If a message run is run before the currently shown run, you can view the history of the previous message run. Procedure 1. Click Connectivity studio Integration operations. 2. On the History errors tab, in the list, find and select the desired message run. 3. Click History. 4. On the Action pane, on the History tab, click Original history. 5. Close the page. 6. Close the page. Solve errors Solve errors Solve the errors that have occurred in the message run. Errors solved and re-run  of message run required? Errors solved and re-run  of message run required? Re-run the message run Re-run the message run If you have solved the errors in a message run, you can run it again. The message is re-run in the company in which it was originally run. As a result: The status of the selected message run is set to Reprocessed. A new message run history record is created for the re-run. Procedure 1. Click Connectivity studio Integration operations. 2. On the History errors tab, in the list, find and select the desired message run. 3. Click History. 4. On the Action pane, on the History tab, click Run. 5. Define how the message is run: - Direct: The message is run immediately. When you click OK, you must wait till the message is processed before you can proceed with your work. - Asynchronous: The message is run (almost) immediately in the background. If you click OK, you can proceed with your work while the message runs. - Batch: The message is run in batch. If you click OK, you can proceed with your work. The message is scheduled and run by the batch framework. In the Run asynchronously field, select an option. Note: If the Run mode is Background or Batch, you must also define the batch group. 6. In the Batch group field, enter or select a value. 7. Click OK. 8. Close the page. Mark message run as Solved Mark message run as Solved If the errors of a message run are solved, and no re-run in History management is required, the message run status is not automatically set to Finished. Therefore, you can mark the message run as Solved. As a result, the message run status is set to Finished. Procedure 1. Click Connectivity studio Integration operations. 2. On the History errors tab, in the list, find and select the desired message run. 3. Click History. 4. On the Action pane, on the History tab, click Solved. 5. Close the page. Run without errors? Run without errors? End End View error report View error report 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. Yes No Yes No

Activities

Name Responsible Description

View message run history

Application Consultant

You can review and analyze the history of message runs.

View message run record history

Application Consultant

 		For each message run, the processed records with errors are shown. For each shown record, you can view the record details. If required, you can change the values to be set.

Show Infolog for run

Application Consultant

 		For each message run with errors, you can open the Infolog and read the related error messages.

View original message run history

Application Consultant

 		If a message run is run before the currently shown run, you can view the history of the previous message run.

Solve errors

Application Consultant

Solve the errors that have occurred in the message run.

Re-run the message run

Application Consultant

If you have solved the errors in a message run, you can run it again. The message is re-run in the company in which it was originally run. As a result:

  • The status of the selected message run is set to Reprocessed.
  • A new message run history record is created for the re-run.

Mark message run as Solved

Application Consultant

 		If the errors of a message run are solved, and no re-run in History management is required, the message run status is not automatically set to Finished. Therefore, you can mark the message run as Solved. As a result, the message run status is set to Finished.

View error report

Application Consultant

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].

Provide feedback