Dynamics 365 Finance & Operations

Microsoft enterprise ERP: financials, supply chain, and OData entity operations

Dynamics 365 Finance & Operations API reference

Signs in with: OAuth 2.0 sign-in
Runs on: Cloud or On-Prem Worker
Operations: 16
Ready-made triggers: 0

Connect Dynamics 365 Finance & Operations

In Neblex open Connect › Connections and click New Connection.
Search for Dynamics 365 Finance & Operations and give the connection a clear name.
Fill in the fields. Secret values are encrypted and never shown again.
Click Test, then Create Connection.

For services offered under Connect a Service you only sign in and approve access. Otherwise use Connect with OAuth2 with your own OAuth app. See Authorize with OAuth.

Field	What to enter
Environment hostRequired	Cloud: myenv.operations.dynamics.com. On-premises: your host + /namespaces/AXSF, e.g. ax.acme.corp/namespaces/AXSF.
Token endpointRequired	Cloud: https://login.microsoftonline.com/<tenant-id>/oauth2/v2.0/token. On-premises: your AD FS token endpoint.
Application (client) IDRequired
Client secretRequiredSecret
ScopeRequired	https://<your-environment-host>/.default

Use it in a flow

Open a flow, open the node library and search for Dynamics 365 Finance & Operations.
Drag it onto the canvas and choose an Operation and your connection.
Map the operation's fields from earlier steps, or click Map with Matt.
Use Test this step to see what it returns, then save.

To start a flow from Dynamics 365 Finance & Operations without a ready-made trigger: a Poll for changes trigger can check one of its list operations on a schedule and pass on only what is new; if Dynamics 365 Finance & Operations can send webhooks, a Webhook trigger receives them at its own URL.

Operations

16 operations in 3 groups. Each one is a step you can add to a flow.

Data Management9

Export to a package`exportToPackage`	POST	Start a DMF export of a data project; returns the execution id.
Generate the target error keys file`generateImportTargetErrorKeysFile`	POST	Create the error-keys file for records that failed staging-to-target; poll the URL op afterwards.
Get an execution's errors`getExecutionErrors`	POST	The error messages of a job execution.
Get an execution's status`getExecutionSummaryStatus`	POST	Unknown, NotRun, Executing, Succeeded, PartiallySucceeded, Failed or Canceled.
Get an upload URL`getAzureWriteUrl`	POST	A writable blob URL (SAS) to upload a data package to.
Get the exported package URL`getExportedPackageUrl`	POST	The download URL (SAS) of a finished export.
Get the staging error file URL`getImportStagingErrorFileUrl`	POST	The error file of records that failed source-to-staging for one entity.
Get the target error keys file URL`getImportTargetErrorKeysFileUrl`	POST	The generated error-keys file's URL (empty while still generating).
Import from a package`importFromPackage`	POST	Start a DMF import from an uploaded data package; returns the execution id.

Entity6

Call an entity action`callEntityAction`	POST	Invoke a bound OData action (SysODataActionAttribute) on an entity set.
Create an entity`createEntity`	POST	Insert a record into any public data entity.
Delete an entity`deleteEntity`	DELETE	Delete a record by its full key.
Get an entity`getEntity`	GET	Fetch one record by key.
List entities`listEntities`	GET	Query any public data entity with OData options ($filter, $select, $expand, $orderby, $top, $skip).
Update an entity`updateEntity`	PATCH	Patch fields on a record by its full key; only the fields you set are sent.

Metadata1

Get entity metadatagetMetadata GET The $metadata document listing every public entity, its keys, fields and enums.