Translate

Saturday, June 26, 2021

🚀 Key Technical Changes from AX 2012 to Dynamics 365 Finance and Operations (D365 F&O)

Microsoft’s shift from AX 2012 to Dynamics 365 F&O is more than just an upgrade—it’s an architectural, development, and deployment transformation. Here's a deep dive into the major visible and underlying technical changes, explained in clear terms.

🔄 Top-Level Visible Changes

In layman terms, these are the three most noticeable differences in D365 compared to AX 2012:

  1. New Web-Based Client
    No more Windows client! D365 is browser-based and runs on all modern devices, including tablets and phones.

  2. Cloud-Native ERP
    D365 is hosted on Microsoft Azure and follows a service-oriented, scalable architecture with automatic updates and high availability.

  3. New Development Stack
    D365 development moves from MorphX to Visual Studio, enabling modern tools, DevOps, and extension-based customization.

🔑 Key Terminologies in D365 F&O

Here are some foundational terms every D365 developer must understand:

  • 📦 Package:
    A deployable unit in D365 that may contain one or more models. It's the basis for deployment and build separation.

  • 📦 Model:
    A collection of metadata and code elements grouped logically. For example, your HR or Sales module may be built as a model.

  • 🧩 Element:
    Any object in the AOT (Application Object Tree).
    Examples: Tables, Forms, EDTs, Enums, Classes.

  • 📁 Project:
    A Visual Studio-level construct that contains the code, metadata, and resources needed to build an application. A project must be linked to one model only.

🧠 Enhanced User Experience

  • New Browser-Based Interface:
    The D365 UI is clean, fast, responsive, and accessible via browser across devices.

  • Mobile Compatibility:
    Users can access real-time business data via phones and tablets using Power Apps or embedded workspaces.

  • Seamless Integration:
    Deep integrations with Microsoft 365, Power BI, Dataverse, and Microsoft Copilot enhance productivity and enable intelligent business processes.

🛠 Key Developer-Oriented Changes

Let’s explore what changed in the development experience for AX developers:

1️⃣ Visual Studio Development Environment

  • AX 2012:
    Development done in MorphX (AX Client). Heavy reliance on AOT layers and model store.

  • D365 F&O:
    All development happens inside Visual Studio, with full support for:

    • C#, .NET components

    • Integrated X++ language support

    • IntelliSense, Git/Azure DevOps, Extensions

📝 MorphX is deprecated. Visual Studio is the default IDE, integrated tightly with Azure DevOps.

2️⃣ Deployment Packages & Layers

  • Deployment uses Deployable Packages, replacing the traditional model store.

  • Layers (SYS, SYP, etc.) still exist, but overlayering is discouraged.

  • Models are assigned to a package and deployed as part of a complete application suite.

📦 A Deployable Package contains binaries, metadata, and configurations used for moving code across environments (Dev → UAT → Prod).

 3️⃣ Extensions over Overlayering

  • In AX 2012, customizing meant directly editing SYS or SYP layer objects.

  • In D365, Microsoft enforces Extensions:
    You use pre/post event handlers, form extensions, class extensions, and table extensions.

  • You subscribe to events (e.g., form control click, business logic execution) rather than overriding them directly.

✅ Extensions allow smoother updates and keep base code untouched, making upgrades safer and Microsoft-supportable.

4️⃣ Form Patterns

  • Mandatory in D365 for UI consistency and accessibility.

  • AX 2012 allowed flexibility; D365 requires you to apply patterns like:

    • Details Master

    • Simple List & Details

    • Parameter

🧱 If a pattern is missing or incomplete, the form will fail compilation. This enforces better UX design.

5️⃣ Data Entities & Integrations

  • AX 2012:
    Used Document Services (AIF) and DIXF for data import/export.

  • D365 F&O:
    Introduces Data Entities—a unified concept that replaces both DIXF and AIF.

Key Features:

  • Can be exposed as OData v4 REST APIs

  • Support JSON format (instead of SOAP/WCF in AX 2012)

  • Easily created using wizards in Visual Studio

  • Used by Power BI, Excel Add-ins, third-party integrations

🔄 All external integrations now use a consistent, scalable, and modern interface—Data Entities via OData or Batch API.

6️⃣ Event-Driven Programming

  • AX 2012 relied on method overrides.

  • D365 introduces an Event Framework:
    You can write event handlers for methods like OnValidatedField, OnClicked, OnInserting, etc.

Example:

[FormControlEventHandler(formControlStr(CustTable, ButtonOK), FormControlEventType::Clicked)]
public static void ButtonOK_OnClicked(FormControl sender, FormControlEventArgs e)
{
    info("You clicked the OK button!");
} 

🧩 Events encourage loose coupling, making your code future-proof. 

🧪 Summary: AX 2012 vs D365 F&O (Developer Changes)

Area

AX 2012

D365 Finance and Operations

Deployment

On-premises

Cloud-first (Azure)

Development IDE

MorphX

Visual Studio

Customization Model

Overlayering

Extensions

Integration

AIF, WCF, DIXF

OData, Power Platform, REST APIs

UI

Windows Rich Client

Web browser + Mobile friendly

Reporting

SSRS, Management Reporter

Power BI, Electronic Reporting (ER)

ALM

Manual deployments, XPOs

Azure DevOps + Lifecycle Services (LCS)

Automation / AI

Not supported

Power Automate, Copilot AI

🔚 Final Thoughts

Dynamics 365 F&O is not just a version upgrade from AX 2012 — it's a completely reimagined platform that supports:

  • Cloud scalability

  • Modern development practices

  • Powerful integrations

  • Better user experience

  • AI and automation readiness

📌 Coming Soon:

"AX 2012 to D365 F&O Migration Roadmap: Tools, Timeline, and Best Practices"

Posted by