Integration, data, and analytics

How IFS Connect (BizAPIs, projections, routing addresses, transformers), custom events, Migration Jobs, and the IFS Aurena REST layer translate into D365 DMF data entities, OData, business events, Azure integration services, dual-write, and virtual entities — with precise parallel mapping for each IFS integration surface.

What you will be able to do

• Map every IFS Connect integration pattern to a D365 equivalent
• Choose the right D365 integration pattern per workload and volume
• Describe dual-write, virtual entities, and business events as the Dataverse integration layer
• Design a D365 data migration architecture using DMF data entities

Introduction

IFS Connect is a full-featured integration platform: it exposes BizAPI projections (REST/OData endpoints over LU data), supports routing addresses that define message paths between systems, uses transformers to map fields between source and target formats, and integrates with message queues for asynchronous delivery.

IFS Connect: BizAPIs, projections, routing addresses, and transformers

BizAPI — a REST/OData projection of an LU, exposing read and write operations on IFS business objects. External systems query BizAPIs to read and post IFS data without direct database access.

IFS custom events and migration jobs as integration triggers

IFS Custom Events fire on LU lifecycle transitions and can trigger integration actions: calling a BizAPI on a remote system, dropping a message to a queue, running a transformer, or calling a PL/SQL procedure. They are the IFS event-driven integration mechanism.

D365 DMF and data entities: the bulk ingress model

The Data Management Framework (DMF) is the canonical mechanism for bulk data operations in D365. Its components:

D365 real-time integration: OData, business events, and Azure

OData — D365 data entities are exposed as OData v4 feeds. External systems can query, create, update, and delete records in D365 using standard HTTP verbs. OData is suitable for low-volume, real-time, synchronous integration — for example, a portal that reads customer balances, or a field service app that creates work orders.

Dual-write, virtual entities, and the Dataverse bridge

D365 and Power Platform share a Dataverse backbone for low-code applications, Field Service, and Customer Engagement. Two integration mechanisms connect D365 to Dataverse:

Integration surface bridge: Aurena, Connect, projections and the target APIs

IFS exposes integration through several surfaces that are often lumped together during discovery. They should be separated because each maps to a different D365 pattern.

Knowledge check

Summary

IFS Connect provides a coherent integration platform: BizAPIs, routing addresses, transformers, and message queues form a consistent model that IFS integration architects know well.