1. To-Increase Dynamics 365 for Finance & Operations
  2. Connectivity studio
  3. Flows

Monitor inbound web service history
Activity Flow

Depending on how you run an inbound web service integration, you can monitor the integration on these levels:

  • Web service action
  • Message
  • File
  • Inbound web service staging table (only applicable if the asynchronous mode of the web service action is 'Batch')
To monitor an inbound web service integration, use the Connectivity studio Integration operations workspace.

Application Consultant Application Consultant Start Start On which level do  you want to monitor  the history? On which level do  you want to monitor  the history? Monitor web service action history Monitor web service action history When a web service action is run, you can view the web service history. The web service history shows, for example, the:Status of the web service action run.Related web service requests.Related message runs.Possible issues can occur, for example, in the:Message run.Connection with the web service. Procedure 1. Click Connectivity studio Integration operations. 2. Review the web service action runs for which errors occurred. Click the Webservice errors tab. Note: You can also click the Web service tab, which shows all web service action runs. 3. In the list, find and select the desired web service action run. 4. Click Web service history. 5. You can view history that is related to the web service action run history. The Web requests tab shows all web requests that are sent during the web service action run. Expand the Details section. Note: You can view detailed information about a web request: - If a web request has an error, select it, and, on the Error tab review the details of the reported error. - For outbound web service actions, you can view the web request header in JSON format. Authorization information is excluded from the header. - For inbound and outbound web service actions, you can view the transferred data in the format as defined by the applicable message. 6. The Message history tab shows all messages that are run for the web service action run. Click the Message history tab. Note: If a message has an error, review the details of the message run. To do so, on the Action pane, on the History tab, click Message history. 7. Close the page. Monitor message 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.

 

@videoref:CS7

 Monitor file history

Monitor file history

You can review and analyze the file history of message runs for messages with an Azure file storage connector. All actions that are done to the related file, are registered in the file history.
Registered file actions are the:
  • Standard file actions related to the Working, Archive, Error, and Split folders. For example, on import, a file is read from the Working folder and when successfully processed, it is moved to the Archive folder. Both the 'read' and the 'move' action are registered.
  • Additional file actions as set up for the Azure file storage connector.
You can monitor the file history from the Connectivity studio Integration operations workspace.

 Monitor inbound web service staging table Monitor inbound web service staging table Depending on the asynchronous execution mode of the inbound web service action, the inbound web service process runs directly or asynchronously.If the asynchronous execution mode is 'Batch' and the web service action is triggered, the data, as received by the web service request, is stored in the Inbound web service staging table.You can monitor the inbound web service staging table. Procedure 1. Click Connectivity studio Integration Design. 2. Click the Web service tab. 3. In the list, find and select the desired inbound web service action. 4. Click Edit. 5. On the Action Pane, click Operation. 6. Click Inbound web service staging. 7. In the list, find and select the desired record. 8. Click Run. 9. Close the page. 10. Close the page. End End Web service action Message File Staging table (only if Asynchronous mode = Batch)

Activities

Name Responsible Description

Monitor web service action history

Application Consultant

 		When a web service action is run, you can view the web service history. The web service history shows, for example, the:
  • Status of the web service action run.
  • Related web service requests.
  • Related message runs.
Possible issues can occur, for example, in the:
  • Message run.
  • Connection with the web service.

Monitor message history

Application Consultant

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.

 

Monitor file history

Application Consultant
You can review and analyze the file history of message runs for messages with an Azure file storage connector. All actions that are done to the related file, are registered in the file history.
Registered file actions are the:
  • Standard file actions related to the Working, Archive, Error, and Split folders. For example, on import, a file is read from the Working folder and when successfully processed, it is moved to the Archive folder. Both the 'read' and the 'move' action are registered.
  • Additional file actions as set up for the Azure file storage connector.
You can monitor the file history from the Connectivity studio Integration operations workspace.

Monitor inbound web service staging table

Application Consultant

Depending on the asynchronous execution mode of the inbound web service action, the inbound web service process runs directly or asynchronously.
If the asynchronous execution mode is 'Batch' and the web service action is triggered, the data, as received by the web service request, is stored in the Inbound web service staging table.

You can monitor the inbound web service staging table.

Activities

Name Responsible Description

Monitor web service action history

Application Consultant

 		When a web service action is run, you can view the web service history. The web service history shows, for example, the:
  • Status of the web service action run.
  • Related web service requests.
  • Related message runs.
Possible issues can occur, for example, in the:
  • Message run.
  • Connection with the web service.

Monitor message history

Application Consultant

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.

 

Monitor file history

Application Consultant
You can review and analyze the file history of message runs for messages with an Azure file storage connector. All actions that are done to the related file, are registered in the file history.
Registered file actions are the:
  • Standard file actions related to the Working, Archive, Error, and Split folders. For example, on import, a file is read from the Working folder and when successfully processed, it is moved to the Archive folder. Both the 'read' and the 'move' action are registered.
  • Additional file actions as set up for the Azure file storage connector.
You can monitor the file history from the Connectivity studio Integration operations workspace.

Monitor inbound web service staging table

Application Consultant

Depending on the asynchronous execution mode of the inbound web service action, the inbound web service process runs directly or asynchronously.
If the asynchronous execution mode is 'Batch' and the web service action is triggered, the data, as received by the web service request, is stored in the Inbound web service staging table.

You can monitor the inbound web service staging table.
Related to Notes

Run inbound web service staging records

 		 

Set up default response text

 		 

Monitor inbound web service history

 		 

Provide feedback