This is the reference document Sapota's Dynamics 365 Finance and Operations team built for itself. Every pattern below comes from a production F&O rollout, upgrade, or extensibility engagement we have shipped. We organized the catalogue as a single hub so an architect joining a new project can scan the table of contents, identify which decisions are still open, and jump to the standalone post that walks through the specific tradeoff.
D365 F&O is the most opinionated platform Sapota works with. The decisions you can defer in Power Platform or Salesforce Marketing Cloud are decisions you cannot defer in F&O without paying interest in production. This guide reflects that reality.
If you are evaluating Sapota for a D365 build, this is what we mean when we say "we have done this before." If you are an architect at another team, this is the syllabus we onboard new senior F&O hires against.
Who this guide is for
Three audiences benefit from this hub differently:
Architects starting on a D365 F&O project. Use the table of contents as a checklist for which decisions you have made consciously and which you skipped. The vast majority of failed F&O projects we have audited could have been steered back on track if a senior architect had walked the equivalent of this list in week one.
CFOs or CIOs evaluating an F&O implementation partner. Skim the section titles. The depth of any consultancy's coverage on these specific operational topics is a reasonable proxy for how many production F&O rollouts they have actually shipped, versus how many demos they have run.
Sapota engineers onboarding to a new F&O client. This is the documented version of what your senior architect will tell you in the first design workshop. Read it, then jump into client-specific context.
The 30 posts linked below cover the full F&O engineering lifecycle: X++ extensibility, reporting and audit, row-level security, supply chain and manufacturing, procurement and finance workflows, project operations, multi-country and industry-specific rollouts, migration and cutover, dual-write to Power Platform, ALM and DevOps, and the Business Central path for smaller subsidiaries.
Section 1: Core extensibility patterns
X++ extensibility in modern F&O is a different practice from AX 2012 overlayering. Chain of Command, event handlers, extension classes, and the Data Management Framework constraints have to be understood at the same level as the underlying business logic.
Posts on the F&O extensibility patterns Sapota uses on every engagement:
- Chain of Command in D365 F&O: Three Production Pitfalls, the three CoC pitfalls that surface in code review and the patterns that prevent them.
- Custom Workflow Providers in F&O: When Built-Ins Run Out, how to extend the F&O workflow framework with custom providers when the out-of-the-box conditions are not enough.
- Number Sequences in F&O: Why Yours Is About to Break, the number-sequence extension pattern and the locking pitfall that surfaces under load.
- Data Entities That Survive DMF Refresh: The F&O Checklist, the entity-design checklist that determines whether a custom entity stays usable after the next platform update.
Section 2: Reporting, audit, and security
F&O reporting is a layered story: SSRS for transactional reports, OData for external integrations, audit trails for compliance, and XDS policies for row-level security. Each layer has its own performance ceiling and its own failure mode.
Posts on the reporting, audit, and security patterns Sapota deploys:
- SSRS Reports in F&O: The RDP + Contract + Controller Pattern, the standard pattern for non-trivial SSRS reports that scales beyond AOT-generated stubs.
- F&O OData v4 Endpoints: Auth, Paging, and $filter Pitfalls, the OData patterns that survive integration with non-Microsoft consumers, including the $filter encoding traps.
- Audit Trails in D365 Without Killing Performance, the audit-trail configuration that meets compliance requirements without crippling transaction throughput.
- XDS Policies in F&O: Row-Level Security That Actually Fires, the Extensible Data Security policy structure that enforces row-level access at the platform layer rather than in business logic.
Section 3: Supply chain and manufacturing
F&O Supply Chain is where the platform earns its license cost (or fails to). The integrations between Engineering Change Management, IoT, MES, warehouse automation, and the omnichannel inventory model are the patterns that decide whether the rollout matches the operational reality.
Posts on the supply chain and manufacturing architecture Sapota ships:
- Product Lifecycle in D365 F&O: Engineering Change Management, the ECM workflow that bridges product engineering and the released-product master in F&O.
- IoT Data into D365 Supply Chain: The Azure-Native Pattern, the IoT Hub plus Stream Analytics architecture that lands sensor data into F&O without overloading the OLTP layer.
- MES Integration with D365 Supply Chain: Azure Middleware Pattern, the Logic Apps middleware pattern that integrates a manufacturing execution system with F&O production orders.
- Warehouse Automation: Service Bus + D365 Business Events, the business-events plus Service Bus pipeline that drives warehouse automation off F&O state changes.
- Omnichannel Inventory Visibility in D365: DOM and the Inventory Add-in, the Distributed Order Management and Inventory Add-in pattern for unified inventory across channels.
- Global Product Catalog in D365: Released Products + PIM Integration, the released-product structure and PIM integration pattern for organizations with thousands of SKUs.
Section 4: Procurement and finance workflows
Procurement and finance workflows are where F&O projects either ship on time or stall in user acceptance. The PO approval matrix, vendor onboarding, and invoice automation are the patterns we revisit on every engagement.
Posts on the procurement and finance patterns Sapota relies on:
- Vendor Invoice Automation in D365: OCR, Matching, Tax Localization, the invoice-automation pipeline including OCR, three-way match, and country-specific tax handling.
- PO Approval at Scale in D365: Rule-Based Procurement Workflows, the rule-based PO approval workflow that scales to organizations with thousands of approvers.
- Centralized Procurement in D365: Global Address Book + Shared Vendors, the global address book and shared-vendor pattern that lets centralized procurement teams negotiate group-wide while local entities still transact.
Section 5: Project Operations and analytics
Project Operations and Customer Insights extend F&O into project-based services and analytics. Each is its own discipline with its own configuration discipline.
Posts on Project Operations and analytics integration:
- Project Governance in D365 Project Operations: Approvals and Audit, the governance setup for project-based service organizations using D365 Project Operations.
- Donor Analytics in D365: Customer Insights + AI Builder + Marketing, the Customer Insights and AI Builder pattern that surfaces predictive donor segments for non-profits running on D365.
Section 6: Multi-entity, multi-country, and industry compliance
Once an F&O rollout extends past a single legal entity, the architecture decisions multiply. Multi-business-unit environment strategy, multi-country legal entity structure, divisional rollouts, and industry-specific compliance each carry their own playbook.
Posts on multi-entity, multi-country, and industry-specific F&O architecture:
- Environment Strategy for Multi-BU D365: Single Tenant, Multiple LEs, the environment topology that supports multiple business units sharing a tenant without operational interference.
- Multi-country D365 Rollout: Legal Entities and Consolidated Reporting, the legal-entity structure and consolidation pattern for organizations operating across multiple tax jurisdictions.
- Replacing Legacy ERP Across Diverse Divisions: Architect's Playbook, the architect's playbook for replacing heterogeneous legacy ERPs across divisions with different operational models.
- Pharma Compliance on D365: LCS BPM + Audit Policies for FDA/EMA, the LCS Business Process Modeler and audit-policy configuration that meets FDA and EMA validation requirements for pharma rollouts.
Section 7: Migration, dual-write, and cutover
The two highest-risk phases of any F&O engagement are the upgrade from AX 2012 and the cutover from a legacy ERP. The patterns below are the playbooks Sapota has refined across multiple of each.
Posts on migration, dual-write, and cutover Sapota uses:
- AX 2012 to D365 F&O Upgrade: Redesign, Don't Re-Overlay, the upgrade rule that overlay code from AX 2012 has to be redesigned as extensions, not lifted-and-shifted.
- Phased D365 Cutover: Dual-Write for Legacy-System Coexistence, the phased cutover pattern that uses dual-write to keep legacy systems alive during the transition.
- Post-Acquisition D365 Onboarding: Interim Connectors First, the interim-connector pattern for onboarding an acquired company into the parent's D365 environment before the full integration completes.
- Dual-Write to Dataverse: The Initial Sync and Cutover Runbook, the dual-write initial sync and cutover runbook for syncing F&O master data to Dataverse.
- Dual-Write Between F&O and Customer Engagement: What It Actually Does, the architecture explanation of what dual-write actually synchronizes between F&O and Customer Engagement, including the gotchas.
Section 8: ALM, DevOps, and Business Central
F&O ALM is unique because LCS sits in the middle of the build pipeline. Business Central is a parallel Microsoft ERP that Sapota uses for smaller subsidiaries that do not need the full F&O footprint, with its own AL extensibility model.
Posts on F&O ALM and Business Central patterns:
- LCS + Azure DevOps: The D365 F&O Build Pipeline That Scales, the LCS-and-Azure-DevOps build pipeline that supports multi-developer F&O teams with deployable packages and source control.
- Business Central AL Extensions: Per-Tenant vs AppSource Path, the AL extension paths in Business Central, when to ship per-tenant and when to publish to AppSource.
Beyond F&O: Power Platform and SFMC
The 30 posts above cover Dynamics 365 Finance and Operations and Business Central. Sapota also runs parallel Power Platform and Salesforce Marketing Cloud engineering practices, each with its own pattern library.
- The Complete Power Platform Engineering Guide, 30 production patterns covering Dataverse modeling, Canvas and model-driven Power Apps, Power Automate, Power BI embed, custom connectors, security, and ALM.
- The Complete SFMC Implementation Guide, 70+ production patterns covering Data Extensions, Content Builder, Journey Builder, Automation Studio, Einstein, deliverability, and Marketing Cloud Connect.
If you are evaluating Sapota for a combined F&O plus Power Platform or F&O plus Customer Engagement engagement, mention it on the call and we will share the integrated playbook directly.
How Sapota uses this guide on a real engagement
Week one of every D365 F&O project, the assigned architect walks the relevant sections of this hub with the client team. The sections we open depend on the engagement scope:
- A new F&O implementation pulls Sections 1, 4, 6, 7, and 8 first.
- A platform upgrade from AX 2012 leads with Sections 7, 1, and 8.
- A supply chain or manufacturing-led rollout pulls Sections 3, 4, 6, and 8.
- A pharma, government, or regulated-industry rollout adds Section 2 and the compliance posts in Section 6.
- A subsidiary on Business Central rather than F&O pulls Section 8 and a focused subset of Section 4.
The conversation surfaces which decisions the client has already made (often without realizing it) and which are still open. By the end of week one, both sides agree on which sections of this guide define the engagement and which are out of scope.
Working with Sapota on D365 F&O
If your team is sizing a D365 F&O implementation, evaluating an active rollout, or auditing a stalled migration, the patterns above are the starting framework. Each section is a standalone deep-dive, and most engagements end up touching five to seven of them.
Reach out via the contact page with the section numbers most relevant to your situation. The first call is usually a forty-five minute review of where the project sits relative to this guide, what is working, and what the next quarter should focus on.
Top comments (0)