How Unit4's integration patterns — direct SQL, SOAP, file-based, Excelerator and Browser export — map to D365's Data Management Framework, OData, Business Events, Azure integration services, and the Power BI and Synapse Link reporting platform.
Unit4's integration model reflects its heritage as a customer-installed, database-accessible ERP. ABW systems are often integrated by direct SQL: another application opens a database connection, reads acrtran for GL transactions, reads acrrelation for master data, and writes back by inserting rows.
[!WARNING] Inventory your entire ABW direct-SQL integration estate before the integration architecture is designed. These integrations embed the ABW Relation+FlexiField schema and will require complete rewrites. They are frequently undocumented — every system that was given SQL read access to ABW is a potential direct-SQL integration.
DMF is D365's structured data movement platform. It operates on data entities — typed, flat projections of D365 business objects designed for import and export. A data entity hides the underlying table complexity: importing a vendor invoice entity populates VendInvoiceInfoTable, VendInvoiceInfoLine, VendInvoiceInfoSubLine and several…
Business Events are D365's mechanism for publishing application lifecycle events to external subscribers. When a purchase order is confirmed, a payment journal is posted, or a project milestone is reached, D365 publishes a lightweight JSON payload to a configured endpoint.
Reporting is an integration concern in D365 because the analytical data model is separate from the transactional model. D365 Finance does not have a built-in query builder like Unit4 Browser. The reporting landscape has four components:
The most important integration architecture decision is the canonical data model: the agreed representation of each shared entity (Vendor, Customer, Project, Cost Centre) across D365 and all connected systems.
Unit4 estates often contain several integration generations at once: ABW direct SQL, SOAP services, File Routes, Excelerator imports, Browser-output capture and newer ERPx REST or event subscriptions. D365 has broad integration coverage, but not as a one-for-one replacement for each habit.
D365 sits in a Microsoft integration fabric that is fundamentally different from Unit4's direct-SQL and file-based heritage. The migration is an architectural redesign, not a repointing exercise: