Skip to main content
This page records how composerID publishes into Microsoft Dynamics 365: the vendor’s API posture, the publish target and field mapping, and the documentation each claim rests on. It is for anyone evaluating the connection or building against it. Dynamics 365 Finance & Supply Chain is a financial-commitment system of record for the outsourced work-order channel. composerID publishes Purchase Order entities through the OData endpoint, carries the Intent ID via an extended field on the entity, and back-syncs create/update/delete activity through Business Events and Data Events.
Category: ERP. Coverage status: Specification mapped. Vendor documentation: public developer portal.

​
Integration path

How composerID connects to this destination, at a glance.

​
Vendor documentation

OData endpoint (finance & operations)

Data entities overview

Data events (CUD notifications)

​
API posture

​
Publish target and field mapping

Each object below pairs the canonical intent fields with the destination’s own fields and operations. The mapping is indicative until it is confirmed against a tenant at onboarding.
Nothing works until the Entra app is mapped to an environment user with the right security roles. Custom fields ride on entity extensions (or custom data entities) - agree the Intent ID field per tenant. Data Events require Power Platform integration on the environment; environments without it fall back to Business Events or polling. OData is for transactional volume - bulk loads belong in the Data Management Framework.

​
Next steps

How composerID connects

The five ways composerID reaches a destination, and the minimum a destination must offer.

Publishing

Plan, preflight and publish: how a decision becomes a valid record in a destination.

All destinations

Every destination composerID documents, with its category and coverage status.