Real-life scenarios, not demo code
Every template and sample comes from integrations that already run in live D365FO environments.
Solution for Microsoft Dynamics 365 SCM and Finance
Build reliable and easy to support Dynamics 365 ERP integrations
An open-source X++ framework for predictable inbound and outbound integrations — one repeatable model for designing, processing, testing, and operating every interface.
Production-proven scenarios100% X++, no external componentsFree and open source
EI External Integration workspaceOperational
Why teams use it
One framework. Every integration lifecycle.
Reusable patterns backed by official documentation and real-world tutorials.
See every message journey
Source payloads, processing status, errors and traces stay together — built for the people who keep integrations running after go-live.
Develop without the external system
Import files manually, replay message payloads, and run processing without a live connector.
How it works
One repeatable model for every interface
The framework helps from the moment you get the task "integrate D365FO with a third-party system": a questionnaire to structure the first design meeting, a template to describe the message mapping, four base flows ready to run, and sample connectors for every common channel.
Design
Ready-to-use templates for integration planning:
- Inbound
- Outbound Event-based
- Outbound Periodic
- Service-based
Load data
Sample connectors for:
- Azure Service Bus
- SFTP
- Azure File Share
- REST API
- AI (LLM)
- Manual upload
Process data
Import documents from CSV, Excel, XML, JSON, PDF. Samples for:
- Sales lines
- Ledger journals
- Purchase lines
- Vendors
Test
Validate before go-live:
- Performance testing up to 1M journal lines
- Run any document manually without a connector
Why External Integration
Read the full comparison →Advantages over the standard tools
vs Data Management Framework
- Support for custom transactions
- Document linked to the original file
- Business logic not tied to data entities
- Native X++ — no external dependencies
- A standard approach to error types
vs Business Events
- Document created at the time of export
- Messages unique per document, no duplicates
- The response can be processed
- Full logs — including successful exports
vs Message Processor
- Enhanced logging and tracing
- Manual message processing
- Testing in a ttsbegin-ttsabort block
- Processing and format flexibility
Use cases
Browse all use cases →Start from a working integration pattern
InboundREST API
Import web sales orders
Incrementally load sales documents from a REST endpoint with mapping, replay, and full traceability back to the original request.
Read the tutorial →OutboundREST APIEvent-based web exports
Create one durable export document per business event, send it to a web service, and keep complete operational evidence.
Read the tutorial →OutboundSFTPPeriodic SFTP export
Generate files from SQL queries, data entities, or X++ procedures and deliver them to SFTP with export logs.
Read the tutorial →Ready to try it?
Install the module and build your first integration.
Use the source, samples, and documentation as the starting point for your next D365FO integration.