Data export to Azure Service Bus queue or topic
Concept
You can use a connector of type 'Service Bus queue' to export data to an Azure Service Bus queue or topic.
Supported Service Bus entities
The 'Service Bus queue' connector supports these Service Bus entities:
- Queue: Queues provide First In, First Out (FIFO) message delivery to one or more competing consumers. That is, receivers typically receive and process messages in the order in which they were added to the queue. And only one message consumer receives and processes each message.
- Topic and subscriptions: Topics and subscriptions provide a one-to-many form of communication in a publish and subscribe pattern. It's useful for scaling to large numbers of recipients. Each published message is made available to each subscription registered with the topic. Publisher sends a message to a topic and one or more subscribers receive a copy of the message, depending on filter rules set on these subscriptions.
For more information, refer to Service Bus queues, topics, and subscriptions.
Service Bus search definitions
If you want to monitor dead letter data from a Service Bus, define dead-letter-specific Service Bus search definitions.Data export to Service Bus queue
You can use the 'Service Bus queue' connector to export data to a Service Bus queue. Make sure that for the connector the:
- Service Bus type is 'Queue'.
- Entity field is filled with the name of the applicable Service Bus queue.
- A message is added to the Service Bus queue.
- Each message that is sent to the Service Bus queue is logged in Connectivity studio. You can view the sent data on the Sent data page.
Data export to Service Bus topic
- Service Bus type is 'Topic'
- Entity field is filled with the name of the applicable Service Bus topic.
- Subscription field is filled with the name of the applicable Service Bus topic subscription. For export, the subscription is not mandatory.
- A message is added to the Service Bus topic.
- Each message that is sent to the Service Bus topic is logged in Connectivity studio. You can view the sent data on the Sent data page.
Document
The target document of the export message defines which data is sent to the Service Bus queue or topic and in which format and structure. So, the document does not result in a file.
With the 'Service Bus queue' connector, you can use these external file-based documents: EDI, Fixed text, Text, XML, JSON. You can only use this connector in combination with a document for which the version 3 (V3) handler class is selected.
Dead letter queue
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. To do so, run 'Receive dead letter data'.
On receiving data from the Service Bus dead letter queue, based on the Service Bus search definitions and settings on the received data, process messages are automatically assigned to the received dead letter data records.
You can monitor the received dead letter queue data on the 'Received dead letter data' page.
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.