Business events and Data Events

In this article, let us understand the concepts business events and Data events - Definition,Use case and limitation

Business events

Enable external systems to receive notifications from D365FO ,allowing automated actions to be triggered in response to specific business processes. These events are initiated when a business process is executed.

These can be consumed by Power Automate and Azure services. So user should have their own PA or Azure subscription. But it is not recommended for heavy payload intended for a data export scenario.

There are many out of box event events which can be used for the implementation or extend the standard event as per the business scenario. It is also possible to create a business event from the scratch if there is no standard one.

Data events:

Are triggered by changes to data within D365FO. These include create, update, and delete (CUD) operations that can be enabled for individual entities. For instance, if the "Create" event is enabled for the CustomersV2 entity, a notification is sent out each time a new customer is created in the system.

All standard and custom entities in finance and operations apps that are enabled for Open Data Protocol (OData) can emit data events. In the data event catalog, each event for an entity is listed as a data event that subscriptions can be established for. The concept of activating the data event and associating it with an endpoint resembles the concept of business events. When a data event occurs, the payload of the event contains the corresponding entity record.

Data entities are available in Power Platform enabled events. Be careful when enabling dual write and data events for the same entity might lead to performance impact. Also activating data events for update events will result in performance degrade .Virtual fields updates are not supported by data events.

The Data events that occur in finance and operations apps are processed asynchronously across multiple systems to deliver them to the target endpoint. Therefore, the order in which they're emitted in finance and operations apps isn't guaranteed to preserve the order in which they're delivered to the endpoints.

The entity properties are included in the event schema. These fields are the properties that make up the virtual table on which the data event is based. The information that is shown includes the field name and label. Business events allows us to download the schema , but data event doesn`t provide the option of download.

Below table gives an quick comparison between the two concepts

INTEGRATION PATTERN:

The integration pattern is similar for both the events - except the data event sends the data to dataverse and can be consumed by a middleware when the dataverse receives the data. This also depends on the Endpoints confugured in D365FO .

Reference:

https://learn.microsoft.com/en-us/shows/dynamics-365-fasttrack-architecture-insights/business-events-and-data-events

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/business-events/data-events

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/business-events/home-page