Integrating with external systems using events

Path: Integration > Integrating with external systems using events · tier official · system integration · narrative reviewed (checked by Opus)

Overview

This area covers two ways for external systems to react to what happens in Business Central. Business events (preview) let partners and customers notify and trigger external systems when actions occur, and they integrate with Dataverse and Power Automate. The page is associated with 2023 release wave 1. Webhooks push notifications when entities change, and are managed through the REST API.

The business events page describes business event subscriptions, custom business events, external webhooks and an event catalog. The webhooks page covers registering, renewing and managing subscriptions on entities. It also covers handshake validation, client state, change types, notification retries and use with custom APIs.

Start with the business events page if you want to trigger Power Automate flows or Dataverse scenarios from business actions. Start with the webhooks page if you need entity-level change notifications through the REST API.

Key points

• Business events are in preview, and the page is associated with 2023 release wave 1.
• Business events notify or trigger external systems when actions occur in Business Central.
• Business events integrate with Dataverse and Power Automate flows, and support custom business events, external webhooks and an event catalog.
• Webhooks push notifications when entities change; the webhooks page references version 19.
• Webhook subscriptions are registered, renewed and managed via the REST API.
• Supported webhook change types are created, updated, deleted and collection.
• Webhook topics include handshake validation, client state and notification retries.
• Webhooks can be used with custom APIs.

Learn pages

• Business events on Business Central (preview): Business events provide our partners and customers a mechanism for notifying and triggering their external systems when actions are done on Business Central
• Working with webhooks: Overview of how to manage subscriptions to Dynamics 365 Business Central.

Videos, posts and code changes

Linked by a Haiku matcher with a grounding quote from the item’s summary (link/topics.ts); machine-generated.

• #10466 Resolve purchase lines to items on exact description match (code change): “Inbound purchase invoice lines now resolve to items”
• #10526 Use BaseApp’s new PO Matching module in E-Documents (code change): “E-Documents now leverages BaseApp’s new PO Matching module”
• #11846 Fix View file on outgoing E-Documents to open the exported file (code change): “Opening the View file action on outgoing E-Documents now retrieves and downloads the exported file”
• #11895 Make Reject Order reachable on inbound sales order drafts and confirm… (code change): “The Reject Order action for inbound sales orders is now accessible directly from the Sales Document Draft page”
• #12055 [E-Documents Core] Show error for unmatched inbound Order Response (code change): “Unmatched inbound PEPPOL Order Responses now produce a descriptive error”
• #12070 Fix inconsistent CLEAN27/CLEAN28 tags in E-Document apps (code change): “E-Document apps now use consistent CLEAN27 and CLEAN28 tags”
• #9124 [E-Document] [Payables Agent] Users can personalize-in the Name column on the draft page (code change): “New OnAfterGetMatchedEntityName integration event for connector apps”
• #9426 [E-Document Formats] Migrate NAV PRs 247170 and 247176 into BCApps (code change): “Migrate NAV PRs into BCApps. PINT A-NZ and Factura-E e-document formats”
• #9637 [Event Requests] Add integration events across base app and SMTP module (code change): “adding new integration events or extra parameters on existing ones in the base application”
• #9872 Add missing telemetry event IDs to E-Document Session.LogMessage calls (code change): “Added missing telemetry event IDs to 21 Session.LogMessage calls in E-Document”

Source: Microsoft Learn (CC BY 4.0). Descriptions are Learn’s own.