Dynamics 365 Finance & Operations REST Connector
API Documentation
Section titled “API Documentation”D365 F&O’s OData v4 endpoints and Data Management Framework document the endpoints and bulk-extract path this connector uses.
How Authentication Works
Section titled “How Authentication Works”The connection authenticates as an application using Entra ID (Azure AD) client-credentials — an app registration’s client ID and secret exchanged for an access token, scoped to the environment’s resource. There is no interactive sign-in.
Configuration
Section titled “Configuration”| Field | Type | Description |
|---|---|---|
| Name | Text | Display name for this connection. |
| Environment URL | Text | Your D365 F&O environment URL, e.g. https://yourorg.operations.dynamics.com. |
| Client ID | Text | The Entra app registration’s application (client) ID. |
| Client Secret | Text | The app registration’s client secret. Stored encrypted. |
| Tenant ID | Text | Your Azure AD tenant ID. |
| Resource/Scope | Text | The OAuth2 scope requested, typically the environment URL plus /.default. |
Entities Available to Import
Section titled “Entities Available to Import”The Import D365 F&O Entity step covers six entities: main_accounts, currencies, customers, vendors, released_products, ledger_journal_headers. Each pull runs in either odata sync mode (a direct call, for routine pulls) or dmf bulk mode (an asynchronous Data Management Framework export job, for large extracts), and supports per-entity server-side filters including date, account, and dimension ranges. See Import D365 F&O Entity for the full field reference.
Posting Journal Entries
Section titled “Posting Journal Entries”The D365 F&O: Post Journal Entry step posts general ledger journal entries through PlaidCloud’s shared ERP write pipeline: submit to D365 F&O’s asynchronous custom-service journal post action, poll to a terminal state, and confirm before reporting an entry posted. A correction posts a new, debit/credit-swapped reversing entry rather than editing the original. See D365 F&O: Post Journal Entry for the field reference, and Connect to Dynamics 365 Finance & Operations for the full posting walkthrough.
Known Limitations
Section titled “Known Limitations”| Limitation | What it means |
|---|---|
| DMF sync mode has extract latency | A dmf pull waits on an asynchronous export job — materially slower than an odata pull of the same size. |
| Dimension filtering is structure-dependent | A financial dimension not part of your account structure isn’t filterable server-side; scope it in your workflow after the pull. |
Related
Section titled “Related”- Connect to Dynamics 365 Finance & Operations (guide) — step-by-step: create the connection, test it, import an entity, and post a journal.
- Import D365 F&O Entity
- D365 F&O: Post Journal Entry
- Review ERP Post History