aurelienclere-365/d365fo-cowork-plugin/d365fo-integration-services

D365FO Integration Services

Map the full integration surface of a D365FO environment or model — OData entities, custom SOAP/JSON services, service groups, business events, and batch jobs — to design or document an integration specification.

When to use

• User is writing an integration SFD and needs to know which D365FO endpoints exist
• User wants to find an existing OData entity or service before building a custom one
• User needs the WSDL / endpoint metadata for a custom service
• User is auditing all integration touchpoints in a specific ISV or custom model
• User wants to compare inbound (service, entity) vs. outbound (business event) options

Workflow

1. Get the full integration report. Call report_integrations() (optionally with

model to scope to one model) — returns counts and names across:

• OData entities (AxDataEntity with IsPublic = Yes)
• Custom services (AxService)
• Service groups (AxServiceGroup)
• Business events
• Workflow types
• Batch jobs

1. Drill into a service. Call get_service(serviceName) — returns operations,

request/response contract classes, and the service group it belongs to.

1. Drill into a service group. Call get_service_group(groupName) — returns

member services and the endpoint URL pattern.

1. Analyze integration design. Call analyze_integration(target) to get a

recommendation on the best integration pattern for the described scenario (OData CRUD, custom service call, business event subscription, DMF package, or Dual-write).

1. Present a summary table per the Output Format.

Output Format

Integration surface summary

Service detail

Integration pattern recommendation

Notes

• OData is the default inbound pattern for CRUD operations — check for a public

data entity before building a custom service.

• Custom services (SOAP and JSON) are for complex transactional operations not

covered by OData (e.g. multi-step posting).

• Business events are for outbound notifications — never for inbound data submission.
• DMF (Data Management Framework) is for bulk imports/exports using data entities.
• Dual-write and Virtual Entities are the preferred patterns for Dataverse/Power Platform

integration — only use custom services as a last resort in that scenario.