If you use Azure Service Bus queues or topics to export data, you can monitor and troubleshoot the Service Bus dead letter data information on several specific pages.
Name | Responsible | Description | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Receive data from Service Bus dead letter queue |
Application Consultant |
If a receiver reads a message from a Service Bus queue or topic subscription, an error can occur. If so, the Service Bus moves the message to the applicable dead letter queue. You can receive the messages from the Service Bus dead letter queue. On receiving data from the Service Bus dead letter queue, based on the Service Bus search definitions and settings on the received data, messages are automatically assigned to the received dead letter data records. The assigned messages are used to further process the dead letter data into D365 FO. For example, you can set a Production order 'On hold' when a dead letter is received on the export of a production order. |
||||||||||||
Monitor data received from Service Bus dead letter queue |
Application Consultant |
You can monitor the data that you receive from an Azure Service Bus dead letter queue. The possible statuses are:
|
||||||||||||
Adjust Service Bus search definitions |
Application Consultant |
You can use Service Bus search definitions to automatically assign Connectivity studio messages to received data records from a Service Bus. |
||||||||||||
Reassign message to data received from Service Bus dead letter queue |
Application Consultant |
If no message is assigned to data that you received from a Service Bus dead letter queue (Received status = Invalid), you must adjust or add Service Bus search definitions for dead letter data. If you have done so, you can retry to assign messages to the received dead letter data records without a message assigned. On reassign, for all received dead letter data records without a message, a matching search definition is searched for. If a matching search definition is found:
|
||||||||||||
Process received dead letter data |
Application Consultant |
If a receiver reads a message from a Service Bus queue or topic subscription, an error can occur. If so, the Service Bus moves the message to the applicable dead letter queue. You can receive the Service Bus dead letter queue data. When received, you can further process this data into D365 FO. For example, you can set a Production order 'On hold' when a dead letter is received on the export of a production order. To further process the received dead letter data, run the messages as assigned to the received dead letter data records. You can run the messages in several ways, as desired. You can run a message by running a:
Note: The assigned process messages must have the 'Service Bus queue' connector as source connector.
|
||||||||||||
Troubleshoot message issues |
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.
|
||||||||||||
Reset status of date received from Service Bus dead letter queue |
Application Consultant |
To import data received from a Service Bus dead letter queue, you run import messages to read data from the 'Received dead letter data' table and import this data into D365 FO. If an import message run finishes with errors, the related received dead letter data record gets the status 'Error'. When you have finished troubleshooting the error, you can reset the received dead letter data record status. You can reset the status:
|