Dynamics 365 EZ

Whether you’re new to X++ or have been working with Dynamics 365 Finance & Operations (D365 F&O) for years, there are small patterns and habits that can make your life much easier. In this post, I’ll share 5 practical X++ tips that I’ve seen repeatedly help in real projects – from safer queries to more maintainable and performance-friendly code. ─── Environment • Product: Dynamics 365 Finance & Operations / Finance and Supply Chain Management • Language: X++ • Context: Customizations, extensions, and integrations in D365 F&O These tips are focused on real-world scenarios you’re likely to encounter in daily development. ─── Tip 1 – Prefer while select with clear field lists It’s very common to see: while select * from salesTable { // do something } This works, but it’s not ideal. Pulling all fields can increase IO and memory usage, especially on big tables. Instead, try to: • Select only the fields you need • Make it explicit and easier to read SalesTable s...

When working with a local virtual machine (VM) downloaded from the LCS portal (VHD image), I encountered an issue despite completing all installation and build steps successfully. Problem Description During the creation of a Purchase Order or Free Text Invoice, the system immediately displayed the following error message and prevented record creation: “The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.” Root Cause This error occurs due to improper initialization of performance counters within the AOSService environment. The counters are expected to be read-only, but the system attempts to access them incorrectly. Resolution The issue can be resolved by executing a PowerShell script that reinitializes the performance counters for the AOSService. Steps: Backup your code, data, any pending works. Stop all the related services. Open PowerShell with administrative privileges. Note : If your AOSService folder is located on a different drive, upda...

Dynamics 365 Finance and operations apps are now hosted on Microsoft Dataverse, so you can provision ERP alongside other Dynamics 365 and low‑code apps directly in the Power Platform admin center or via API/PowerShell.  Templates streamline environment creation by preinstalling ERP workloads, and a dedicated Provisioning app adds ERP capabilities to existing environments that already have Dynamics 365 apps enabled. 1. Prerequisites and licensing Licenses : You must have a related Dynamics 365 ERP license (e.g., Finance, Supply Chain Management, Project Operations, Commerce) or the Dynamics 365 Operations Application Partner Sandbox. Admins with the Power Platform Administrator or Dynamics 365 Administrator role can create/manage environments without a full user license, subject to a ~12‑hour cache delay after role assignment. Capacity : At least 1 GB available in both Operations and Dataverse database capacities is required. Environment type: Use Sandbox or Trial (subscription‑bas...

Macros in X++ are precompiler directives that let you define reusable symbols, values, or code fragments before compilation. They are powerful but considered legacy, so Microsoft recommends using language constructs instead. 🔑 Key Points About X++ Macros What Are Macros? Macros are processed before compilation: The compiler never sees the directive itself, only the expanded characters. Legacy feature: They may be deprecated in future releases. Prefer constants or constructs like SysDa for queries. Defining Macros Syntax: #define.MyMacro(Value)   // macro with value #define.AnotherMacro()   // macro without value Case-insensitive: Macro names and directives are not case-sensitive, but best practice is to start names with uppercase. Conditional checks: #if.MyMacro // Code included if defined #endif #ifnot.MyMacro // Code included if not defined #endif Removing Macros #undef removes a macro definition: #undef.MyMacro Using Macro Values Macros can hold character...

For local development in Dynamics 365 Finance and Supply Chain Management (FSCM) , developers typically download and install the Virtual Hard Drive (VHD) from the Lifecycle Services (LCS) - Shared Asset Library . By default, the DEV VHD is configured to run entirely on the C: drive, which has a limited capacity of approximately 126 GB . This drive fills up quickly, especially when working with source code and packages. To avoid space constraints, you can add a new disk to your VM and relocate the AOSService folder. This guide walks you through the process step by step. Step 1: Add a New Hard Drive Open Hyper-V Manager on your host machine. Attach a new virtual hard drive to your development VM. We may need to turn it off first.                Open Computer management to format the new disk. Step 2: Stop D365 FSCM Services Before moving files, stop all related services to prevent conflicts: ...

🚀 Upgrading Dynamics 365 FSCM (F&O) Dev local VM (VHD) to the Latest Service Pack - December 2025 Recently, Microsoft has released the new service update (10.0.40) for Dynamics 365 FSCM (F&O). K eeping your Dynamics 365 FSCM (F&O) development VM up to date is necessary as each service update brings bug fixes, performance improvements, and new features. In this guide, I’ll walk you through upgrading your local VHD to the latest service pack. Prerequisites Before starting, make sure you: Backup your VM (snapshot or export the VHD). Check your current version under System Administration > About. Access Lifecycle Services (LCS) with appropriate permissions. Step 1: Download the Latest Service Update Log in to Lifecycle Services.  Navigate to Shared Asset Library. Select Software deployable package. Download the latest service update (e.g., First Release Service Update 10.0.46) Step 2: Apply the Update on the Dev VM (VHD) Copy the .zip package into your VM (e.g., C:...