Reference · built on requestConnectorERP & finance

Microsoft Dynamics 365 Finance

Public data entities, OData actions, and business events from Dynamics 365 Finance and its finance and operations apps.

Request accessPricing ↗

About

Dynamics 365 Finance runs on the finance and operations apps platform. Its OData endpoint, the /data path under your environment's root URL, exposes every data entity marked IsPublic with create, read, update, and delete, plus bound actions and a read-only REST metadata service. Business events, activated from the catalog under System administration, deliver notices such as Vendor invoice posted and Purchase order confirmed to Azure Service Bus, Event Grid, Power Automate, or other endpoints.

An operator on Fibric reads customers, vendors, invoices, and payments across legal entities, listens for posted and confirmed events, and proposes entity updates for your approval. The record kept with each proposal shows what changed, why, and how to reverse it.

This is a reference listing. It documents what Fibric would read from Microsoft Dynamics 365 Finance and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Any data entity marked IsPublic, read at /data/<EntityName> with $filter, $select, $expand, and $top
  • Records across legal entities with ?cross-company=true and a dataAreaId filter
  • Procure to pay events: Vendor invoice matched, Vendor invoice posted, Vendor payment posted, Purchase order confirmed, Purchase order received
  • Quote to cash events: Invoice created from a sales order, Free text invoice posted, Payment posted, Transaction written off, Collection letter created
  • Entity and label metadata from the read-only REST metadata service at /Metadata
  • Workflow business events, such as approval of a purchase requisition

Proposed actions

  • Target capability: propose creating or updating a record on a public data entity with POST, PATCH, or PUT
  • Target capability: propose calling a bound OData action exposed on a data entity
  • Target capability: propose a set of related writes in one $batch changeset so they succeed or fail together

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Hold payment when a vendor's bank details change

    Watch vendor entities for bank account edits, pause matching invoices, and route the change to a second approver.

    With Vendor Bank Change, Three-Way Match

  • Chase a purchase order that never arrived

    Pair Purchase order confirmed with Purchase order received events and draft the supplier chase when the gap passes the promised date.

    With PO Chase, Inbound Delay

  • Start collections the day an invoice posts

    React to Invoice created from a sales order and Payment posted events to keep the reminder sequence current.

    With Dunning Cadence, Cash Application

Requirements

  • A Dynamics 365 Finance online environment
  • A Microsoft Entra app registration with the Microsoft Dynamics ERP permissions, entered under System administration > Setup > Microsoft Entra applications
  • A dedicated service account user mapped to the app, with security roles for the entities it touches
  • Your own Azure Service Bus, Event Grid, or Power Automate subscription to receive business events
Authentication
OAuth 2.0 through Microsoft Entra ID, using the authorization code flow or client credentials (shared secret or certificate), with the app registered under Microsoft Entra applications in the ERP.

Limits

  • Per user, per app, per web server: 6,000 requests and 1,200 seconds of execution in a 5-minute window, 52 concurrent; 429 when exceeded
  • Pages return at most 10,000 records; $expand goes one level deep; the has and in operators are unsupported
  • Business events arrive out of order and are not meant to carry large payloads
  • Priority-based throttling ranks integrations Low, Medium, or High per app or user when server resources run short

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Microsoft Dynamics 365 Finance ↗

Questions and answers

Which entities can the connector read?
Any data entity whose IsPublic property is true appears under the /data path of your environment root. Its REST metadata service lists them at /Metadata/DataEntities. Every field in the entity key must be supplied to address one record.
How do business events reach an external system?
You activate events in the business events catalog and assign endpoints. Supported endpoint types include Azure Service Bus, Azure Event Grid, and Power Automate. Each payload carries a control number so a consumer can detect duplicate delivery.
What does a throttled request look like?
The service returns 429 Too Many Requests with a message naming the limit hit, for example 6000 requests over 300 seconds. Clients should honor the Retry-After interval before sending again.
Ask about Microsoft Dynamics 365 Finance

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Microsoft Dynamics 365 Finance through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy