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

Receive data from Service Bus queue or topic subscription
Application task

You can use the 'Service Bus queue' connector to import data from a Service Bus queue.

To import data, first receive the data from a Service Bus queue or topic subscription. The received data is added to the 'Received data from queue' table in Connectivity studio.
On receiving data from the Service Bus:
  • Based on the Service Bus search definitions and settings on the received data, import messages are automatically assigned to the received data records.
  • You can use 'peek lock'. If you use 'peek lock', the received Service Bus messages are temporarily locked in the Service Bus queue or topic subscription.


Standard procedure

1. Go to Connectivity studio > Inquiries > Service Bus queue > Received data.
2. On the Action Pane, click Operation.
3. Click Receive data
4. Define the connector that is used to receive Service Bus data.
The connector defines where to receive the data from:
- Service Bus namespace
- Queue or topic subscription
- Authentication
  In the Source connector field, enter or select a value.
5. On receiving data from an Azure Service Bus queue or topic subscription, these receive modes are supported:
- Receive and delete (Peek lock = No)
- Peek lock (Peek lock = Yes)
If you use 'Peek lock' when you receive Service Bus data, the received Service Bus messages are temporarily locked in the Service Bus queue or topic subscription.
  Select Yes in the Peek lock field.
6. Define the number of Service Bus messages to be read from the queue or topic subscription.
If the number is '0', all messages are read from the queue or topic subscription.
  In the Number of messages field, enter a number.
7. If you use 'peek lock', define the number of hours after which the Service Bus messages are automatically unlocked on the queue or topic subscription.
Define a number of hours during which Connectivity studio usually must have processed the data. Resulting in the Service Bus message being:
- Removed from the queue or topic subscription (when processed successfully).
- Moved to the Service Bus dead letter queue (when processed with errors).
  In the Reschedule message (hrs) field, enter a number.
8. Sub-task: Set recurrence.
  8.1 You can receive data from a Service queue or topic subscription in batch in a recurring pattern.
  Expand the Run in the background section.
  8.2 Select Yes in the Batch processing field and fill in the other fields as desired.
  8.3 Click Recurrence.
  8.4 Fill in the recurrence settings as desired and click OK.
  8.5 Click OK.

Notes

You can also use the 'Receive and process data' process. This process:

  1. Receives the data from the Service Bus queue or topic subscription.
  2. Runs the messages that are automatically assigned to the received Service Bus data records.
You can indicate which data you want to receive:
  • Queue or topic subscription data. If 'Yes', you can also use the peek lock function.
  • Dead letter data. You cannot use the peek lock function for dead letter data.

Related to Notes

Monitor and troubleshoot Service Bus import

 		 

Run integration

 		 

See also

Provide feedback