Question

Your organization uses a custom order-management model-driven app. When an order reaches the 'Shipped' status, several downstream systems (a warehouse system, a customer notification service, and an analytics pipeline) need to react. These subscribers are added and removed frequently, and the developers do not want to modify or redeploy Dataverse code each time a new subscriber is introduced. You want to publish a well-defined, discoverable event from Dataverse that any authorized consumer can subscribe to independently. Which approach should you implement?

Accepted Answer

Define a custom API configured as a Dataverse business event and have consumers subscribe to it, raising the event from server-side logic when the order is shipped.

Answer

Register a synchronous plug-in on the Update of the order table that calls each downstream system's HTTP endpoint in sequence.

Answer

Create a cloud flow with a Dataverse trigger that hard-codes an HTTP action for each downstream subscriber.

Answer

Add a webhook step in the Plug-in Registration Tool for each subscriber on the order Update message.