AI and automation in Dynamics 365 F&O: what is practical today
A practical view of AI and automation in Dynamics 365 Finance & Operations — Copilot, business events, Power Automate and the data foundations they depend on.
3 min read
Microsoft Dynamics 365 F&O consulting & engineering
Codefine designs, implements, extends, integrates, optimises and supports D365 F&O. One focused team with more than 20 years of Dynamics AX and Dynamics 365 experience — from the first architecture decision to the thousandth production batch run.
20+ years
Dynamics AX and D365 F&O experience
D365 F&O focused
One platform, known in depth
Technical + functional
Process and code in one team
Architecture to support
From blueprint to long-term operation
Core capabilities
Six capabilities cover most of what our clients ask for. Each one is delivered by engineers who understand both the business process and the code underneath it.
01
The technical and functional blueprint for D365 F&O — modules, data, integrations, security and extensions decided before they become expensive to change.
02
Module setup, data migration, testing and go-live for finance, procurement, warehouse, manufacturing and project operations.
03
Incident handling, monitoring, batch and integration health, service-update validation and continuous improvement after go-live.
04
Slow forms, batch jobs, reports and integrations traced to their cause in X++, SQL, data volume or batch design — then fixed.
05
Upgrade-safe X++ extensions, data entities, services and batch processes — plus connected .NET and Power Platform components.
06
OData, custom services, business events, recurring data jobs and Azure Integration Services — designed for volume, failure and monitoring.
D365 engineering
Functional consultants decide what the system should do. Whether it keeps doing it at volume, through every service update, depends on engineering. That is where Codefine spends most of its time.
Extensions, Chain of Command, SysOperation batch services and set-based data access.
Query plans, index design, blocking chains and data-volume growth.
Legal entities, financial dimensions and master data ownership.
OData, custom services, business events and Service Bus queues.
Batch groups, threads, task bundling and scheduling windows.
Upgrade-safe extension strategy, environments and ALM.
Logic Apps, Functions, API Management and DevOps pipelines.
Dataverse, virtual tables, dual-write and governed flows.
class CFInvoiceSyncService extends SysOperationServiceBase
{
public void process(CFInvoiceSyncContract _contract)
{
CustInvoiceJour invoice;
// Fetch only the fields the integration needs
while select RecId, InvoiceId, InvoiceAccount from invoice
where invoice.InvoiceDate == _contract.parmInvoiceDate()
{
CFInvoiceEvent::newFromInvoice(invoice).send();
}
}
} Execution trace
Illustrative trace structure — not measured data.
Delivery lifecycle
The same engineers who design the solution stay to measure it, optimise it and support it — so knowledge is not lost at every hand-over.
01
We map business processes, pain points, the current system landscape and what success has to look like.
02
We define the D365 F&O solution model: modules, data, integrations, security, environments and performance.
03
We configure, develop, test and deploy with clear ownership, controlled releases and go-live readiness checks.
04
We measure how the system behaves under real load and remove bottlenecks in code, queries and batch design.
05
We stay after go-live: incident handling, monitoring, change requests and continuous improvement.
Performance & reliability
A slow posting can spend its time in X++ logic, in one expensive query, waiting on a lock held by a batch job or calling another system. Measuring first tells us which — and the fix follows the evidence.
Heavy data sources, display methods and grids that load more than they show.
Scans where a seek was expected, missing indexes and parameter-sensitive plans.
Serialised tasks, competing jobs and overnight runs that drift into the morning.
Report data providers that read row by row and temporary tables that grow.
Queries inside loops, missing set-based operations and caching that never hits.
Synchronous calls in posting logic and entities processed one record at a time.
Technology ecosystem
We work across the technologies that surround Finance & Operations — and we know which ones a requirement really needs.
Experience
Our team has worked with Dynamics AX and Dynamics 365 for more than 20 years. Knowing how the platform evolved — and why — makes upgrades, legacy code and modern architecture decisions far less risky.
2006
Axapta becomes Microsoft Dynamics AX. X++ and the AOT are the core of ERP customisation.
2008
Role centres and a broader functional footprint across finance, trade and production.
2011
Model store, new data model and the R2/R3 releases that many companies still run today.
2016
The cloud generation: browser client, Lifecycle Services and Azure-hosted environments.
2019
Continuous service updates and an extension-only model replace overlayering for good.
Today
F&O converging with Power Platform, Dataverse, Fabric and Copilot capabilities.
Milestones show Microsoft's public product history, not individual Codefine projects.
Insights
Practical writing on performance, architecture, integrations, analytics and delivery — from the people doing the work.
A practical view of AI and automation in Dynamics 365 Finance & Operations — Copilot, business events, Power Automate and the data foundations they depend on.
3 min read
What digital transformation means for an ERP-centred business, and how to build a phased Dynamics 365 Finance & Operations roadmap that delivers value.
3 min read
How we investigate slow Dynamics 365 Finance & Operations forms, postings and batch jobs — from defining the scenario to tracing X++ and SQL.
4 min read
Tell us about your environment — a planned implementation, a performance problem, an integration that keeps failing or an AX system that needs a future. You will speak with someone who can answer technical questions on the first call.