The Microsoft ERP ecosystem, from the database up

Finance, Supply Chain Management, Project Operations and the shared application platform underneath them. Delivered as a Microsoft-operated cloud service with continuous service updates, so customisations have to be built as extensions that survive every update.

• Finance
• Supply Chain Management
• Project Operations
• Service updates
• Environments & ALM

Used in D365 F&O Solution Architecture · ERP Implementation & Configuration · Support & Managed Services

Years of AX work mean we read legacy overlayered code, data models and batch setups fluently. That matters when you are stabilising an AX 2012 estate, or planning the move to D365 F&O where overlayering must be replaced by extensions and data has to be upgraded.

• AX 2009
• AX 2012 R3
• Overlayering → extensions
• Data upgrade

Used in Digital Transformation Consulting · Custom Software Development

Chain of Command and event-handler extensions, data entities, SysOperation batch services, custom services and workflow. We write set-based X++ (insert_recordset, update_recordset), design caching deliberately and keep business logic out of form code.

• Chain of Command
• SysOperation framework
• Data entities
• Custom services
• Best-practice checks

Used in Custom Software Development · Performance Optimization

C# libraries referenced from X++, Azure Functions for integration logic, and supporting tools such as file processors or API adapters — kept small, testable and deployed through the same pipeline discipline as the ERP code.

• C# class libraries
• Azure Functions
• API adapters
• Unit testing

Used in Custom Software Development · Integration & API Development

Query plans, index design in the application metadata, statistics, blocking and data volume. In the cloud the production database runs on Azure SQL, so analysis works through the platform's performance tooling and query history rather than direct production access.

• Query plans
• Index design
• Blocking & locking
• Data volume & cleanup

Used in Performance Optimization · Power BI & Business Intelligence

Logic Apps, Functions, Service Bus and API Management for integration; Key Vault for secrets; storage and data services for exports and analytics; Azure DevOps for source control, builds and release pipelines.

• Logic Apps
• Service Bus
• Functions
• API Management
• Azure DevOps

Used in Integration & API Development · D365 F&O Solution Architecture

Choosing the right pattern per flow: OData for transactional reads and writes, custom services for logic-heavy calls, business events for outbound notifications, and recurring data-management jobs for high-volume batch exchange — with retries, idempotency and monitoring designed in.

• OData
• Custom services
• Business events
• Recurring integrations
• Dual-write

Used in Integration & API Development

Standard and custom entities for the data management framework, OData and Excel. Entity design affects throughput directly — set-based processing, staging validation and sensible field mapping matter as much as the business rules.

• Data management framework
• Custom entities
• Data migration
• Staging & validation

Used in Integration & API Development · ERP Implementation & Configuration

Semantic models and DAX measures over finance, supply chain and project data; row-level security aligned with ERP roles; and a deliberate choice of data path — exports to a data lake or Microsoft Fabric rather than ad-hoc queries against the transactional system.

• Semantic models
• DAX
• Row-level security
• Data lake / Fabric
• Embedded workspaces

Used in Power BI & Business Intelligence

Canvas and model-driven apps for scenarios the ERP client does not serve well — field data capture, simple requests, mobile checklists — connected through the F&O connector, virtual tables or dual-write, depending on the data and latency involved.

• Canvas apps
• Model-driven apps
• Dataverse
• Virtual tables

Used in Power Platform Applications

Flows triggered by D365 F&O business events or schedules: approvals, notifications, document routing and hand-offs to other systems — with error handling and ownership defined so flows do not become invisible production dependencies.

• Business-event triggers
• Approvals
• Notifications
• Governance

Used in Power Platform Applications · Integration & API Development