Summary

  • 3 minutes

You now have the skill to get Dataverse events to external services, choosing the publishing and listening mechanism that fits a given need instead of defaulting to a single approach.

What you learned

  • You publish a Dataverse event directly in plug-in code by calling IServiceEndpointNotificationService, giving you a conditional check that only posts when the data meets a specific business rule.
  • You publish a Dataverse event without writing code by registering a service endpoint step in the Plug-in Registration Tool. That step posts unconditionally for every occurrence of the message and table you register.
  • You register the destination a publishing mechanism reaches. That destination might be a webhook for a direct point-to-point call, or an Azure Service Bus namespace for a durable queue a single process drains. It could also be an Azure Event Hubs namespace for a high-volume stream multiple consumers read.
  • You evaluate a destination's response-timing, volume, and consumer needs to recommend the right listening option among webhooks, Azure Service Bus, and Azure Event Hubs for a given integration scenario.

Learn more