Analytics
Power BI on Dynamics 365 F&O: choosing the right data path
Fabric/data lake export, BYOD or OData: choosing the path from D365 F&O to Power BI, and reconciling totals before anyone sees a report.
Dynamics 365 Finance & Operations specialists
Codefine is an İstanbul-based team of D365 F&O consultants and X++ developers. We have worked on Dynamics AX and Dynamics 365 projects for more than 20 years — rollouts, integrations, slow month-end batches, and the support that comes after go-live.
Finance & Operations · X++ · Azure · Power Platform What we do
Each one is handled by people who understand the business process and the X++, SQL and integrations 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.
How we work
No layers of account management. The consultants and developers in the first conversation are the ones who read your code, check the query plans and join the cutover call. We work alongside your IT team and key users, on projects, on ongoing support, or both.
Engineering
Plenty of D365 problems can only be fixed in X++, SQL or the integration layer. That is where most of our time goes.
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.
Performance
A slow posting can be X++ logic, one bad query, a lock held by a batch job or a call to another system. We measure first, then fix the part that is actually slow.
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.
How projects run
Nobody hands your project over to a different team after go-live.
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.
Experience
From AX 4.0 to today's cloud Finance & Operations. That history helps when you are upgrading from AX or maintaining code someone wrote ten years ago.
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 are Microsoft's public product history, not individual Codefine projects.
Insights
Written by the people who do the work: batch and SQL performance, X++ tracing, integrations, and the data paths behind Power BI reporting.
Performance
How we work through a slow posting, form or batch job in D365 F&O: reproduce it, find the dominant layer, trace X++ and SQL, fix the biggest cost first.
In this guide
Analytics
Fabric/data lake export, BYOD or OData: choosing the path from D365 F&O to Power BI, and reconciling totals before anyone sees a report.
Automation
Copilot, business events and Power Automate in D365 F&O: what each can do, what it needs from your data and processes, and where to begin.
Send a few lines about your setup and what is going wrong. You will get a reply from someone who works on Finance & Operations every day.