Skip to main content
Technical Preview

Overview

A client-mode connector for a curated manufacturing / inventory / maintenance slice of Dynamics 365 Finance & Operations OData under https://{env}.operations.dynamics.com/data/: BASE_ADDRESS is the F&O OData root (https://{env}.operations.dynamics.com/data). Topics use erp/dynamics365-fscm/<object>/<verb>.
This is Finance & Operations / Supply Chain, not Dataverse. For CRM Web API (accounts, incidents, Field Service), see Dynamics 365 (Dataverse).
F&O OData requires a real environment URL and an Entra ID OAuth 2.0 Bearer token (client credentials). This template has not been verified against a live tenant. Prefer Hub secrets for tokens. Discover public entities with GET .../data/ or GET .../data/$metadata.

Basic Syntax

Events

Auth

OAuth 2.0 client credentials (Entra ID) — default in the template:
  1. Register an app in Microsoft Entra ID; create a client secret; grant Dynamics ERP API permissions as required by your tenant.
  2. In F&O: System administration > Setup > Microsoft Entra applications — add the client ID and map it to a service user.
  3. Request a token:
  1. Pass the access token on the MQTT request payload:
The connector sends Authorization: Bearer {value.json.access_token}. Prefer Hub secrets / GET SECRET. Never commit real tokens.

Cross-company and keys

By default OData returns only the service user’s default company. The GET endpoints append cross-company=true. To filter one company: $filter=dataAreaId eq 'usmf' with cross-company=true. Entity keys usually include dataAreaId plus a business key (e.g. ProductionOrderNumber) — see Microsoft Learn OData addressing.

Entity name notes

Public collection names can differ by F&O version. This package uses documented PublicCollectionName values from dynamics.fo and community usage. Always confirm on your tenant with GET https://{env}.operations.dynamics.com/data/$metadata or Excel workbook designer. Report-as-finished and inventory journal posting may require a bound OData action after create — loading the journal line alone does not always post.

Deploy

  1. Copy Dynamics365FscmRestApi.lot (no ADD METADATA).
  2. Replace YOUR_ENV in BASE_ADDRESS.
  3. -addRoute on the broker (or Hub deploy).
  4. Publish JSON to a request topic; subscribe to the matching /response topic.
Hub catalog metadata (icon, description, STATUS "beta") is in hub-metadata.lot for Hub / -listTemplates only.

Status

Blocked until a live authenticated call succeeds (factory has no F&O env URL or Entra credentials). Unblock with lab env URL + client-credentials token, then smoke GET /ProductionOrderHeaders?$top=1&cross-company=true expecting HTTP 200.

References

Last modified on October 21, 2026