Message types
A message type is one configured integration: what the payload contains, where it comes from or goes to, and what should happen in D365FO. Every integration built with the framework is one of four templates, each with its own base class and setup form:
| Template | Base class | Direction | Setup form |
|---|---|---|---|
| Inbound | DEVIntegProcessMessageBase | External system → D365FO | Inbound message types |
| Outbound Event-based | DEVIntegExportMessageBase | D365FO → external, per document | Outbound message types |
| Outbound Periodic | DEVIntegExportBulkBase | D365FO → external, per run | Outbound message types |
| Service-based | DEVIntegServiceExportBase | Synchronous request/response | Service message types |
The message type is completely separated from the connector (transport) and the file format (payload parsing) — the same business logic works over any channel, including manual load for testing.
All sample implementations live in the DEVExternalIntegrationSamples model on GitHub.