<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jeffrey Bulanadi on Medium]]></title>
        <description><![CDATA[Stories by Jeffrey Bulanadi on Medium]]></description>
        <link>https://medium.com/@jeffreybulanadi?source=rss-644f82ae8dc3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*79CmP5Ys1Gj4VKpqhCNAvw.jpeg</url>
            <title>Stories by Jeffrey Bulanadi on Medium</title>
            <link>https://medium.com/@jeffreybulanadi?source=rss-644f82ae8dc3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 00:27:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jeffreybulanadi/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Convert Microsoft D365 Business Central Permission Sets into AL Permission Set Objects in Minutes]]></title>
            <link>https://medium.com/@jeffreybulanadi/convert-microsoft-d365-business-central-permission-sets-into-al-permission-set-objects-in-minutes-8a2026ea5273?source=rss-644f82ae8dc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a2026ea5273</guid>
            <category><![CDATA[business-central]]></category>
            <category><![CDATA[msdyn365bc]]></category>
            <dc:creator><![CDATA[Jeffrey Bulanadi]]></dc:creator>
            <pubDate>Mon, 26 Oct 2026 18:20:43 GMT</pubDate>
            <atom:updated>2026-10-26T18:20:43.931Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HqrRisXE9M9MfXdziCuXvQ.png" /></figure><p>A free browser tool that turns your user-defined permission sets into clean AL code with real table names</p><p>Your user-defined permission sets can be AL permission set objects in a few minutes, with real table names and not just numbers.</p><p>On a client upgrade project, one of my tasks was to convert the client’s user-defined permission sets into AL permission set objects. I did it the hard way first, with an exported object list and a Python script. It worked, but only I could use it. So I turned it into a simple web page that anyone on the team can use.</p><p><strong>What It Does</strong></p><p>✔️ <strong>Works with the XML export and Excel/CSV files.</strong> Export your permission sets from the Permission Sets page, or export a permission set to Excel and save it as CSV.<br>✔️ <strong>Real table names from your .alpackages symbols.</strong> Drop in the .app files from your AL project, and `tabledata 17` becomes `tabledata “G/L Entry”`.<br>✔️ <strong>One .al file per permission set.</strong> Download everything as a zip, ready to copy into your AL project.<br>✔️ <strong>Runs in your browser.</strong> Nothing to install, and your files never leave your computer.<br>✔️ <strong>Easy enough for functional consultants too.</strong> No scripts and no command line.</p><p><strong>How to Use It</strong></p><p>1. Export your permission sets from Business Central as XML, or as CSV from Excel. <br>2. Drop the files into the tool.<br>3. Drop in the .app files from your .alpackages folder to get real names.<br>4. Click Download all and copy the .al files into your AL project.</p><p>Full write-up with screenshots: <a href="https://learnbeyondbc.com/blogs/convert-user-defined-permission-sets-to-al-permission-set-objects">https://learnbeyondbc.com/blogs/convert-user-defined-permission-sets-to-al-permission-set-objects</a></p><p>Try the tool: <a href="https://jeffreybulanadi.github.io/bc-permissionset-converter/">https://jeffreybulanadi.github.io/bc-permissionset-converter/</a></p><p>Source code: <a href="https://github.com/jeffreybulanadi/bc-permissionset-converter">https://github.com/jeffreybulanadi/bc-permissionset-converter</a></p><p>Free, MIT licensed, and open source. Give it a try on your next upgrade and let me know how it goes.</p><p><em>*Follow me for more practical insights on Microsoft Dynamics 365 Business Central, AL development, and the surrounding ecosystem.*</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a2026ea5273" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Postman Collection for the Business Central API v2.0]]></title>
            <link>https://medium.com/@jeffreybulanadi/a-postman-collection-for-the-business-central-api-v2-0-eb21df9fc8ef?source=rss-644f82ae8dc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb21df9fc8ef</guid>
            <category><![CDATA[business-central]]></category>
            <category><![CDATA[d365-business-central]]></category>
            <category><![CDATA[msdyn365bc]]></category>
            <dc:creator><![CDATA[Jeffrey Bulanadi]]></dc:creator>
            <pubDate>Wed, 22 Jul 2026 20:37:53 GMT</pubDate>
            <atom:updated>2026-07-22T20:37:53.095Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oWx3FjRJkMLLL0Lz6ZB3JQ.png" /></figure><h3>A ready to use collection covering Business Central API v2.0 endpoints</h3><p>Yo BC Devs,</p><p>I have been working on a project recently that involves a lot of Business Central API work and integrations, and because of that it took me some time to write a blog post.</p><p>After a while I noticed I was setting up the same things again and again like token request, authentication, variables, and a few common API calls before I could even start testing the actual endpoint that I needed.</p><p>So I decided to make something that would save me (and hopefully others) a bit of time. That said, i put together a Postman collection that already has all the basics in place.</p><p>It covers the standard BC API v2.0 and includes all the requests you will find in Microsoft documentation online.</p><p>So the idea is once you enter your tenant ID, client ID, and client secret, you can generate a token and start making requests straight away.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*m8z2yhCp3nebUKZf.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mZXTyBr3-sWdAlMK.png" /></figure><h4>If you are unsure how to create an app registration</h4><p>If you are not familiar with creating an app registration in Entra ID, I have a separate blog that walks through the full setup step by step. You can check it here:</p><p><a href="https://learnbeyondbc.com/blogs/bc-oauth2-setup-and-automation-part-1">OAuth2 Setup and Automation — Part 1: Register Your Entra App, Assign Business Central Permissions, and Prepare for OAuth2 Token Testing</a></p><h4>What does it include?</h4><p>It includes all API endpoints you will find in the <a href="https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/api-reference/v2.0/">BC API v2.0 docs</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*J8Q6MkXwxXFCRPG5.png" /></figure><p>Customers, vendors, companies, journals, dimensions, fixed assets, sales documents, purchase documents, and everything else are already organised into folders.</p><p>The idea was not to create a Postman collection with lots of custom logic or automation. I just wanted something I could import and use without spending the first 20 minutes setting everything up again.</p><h4>Authentication</h4><p>The collection includes a request for generating an access token using the client credentials flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*H33pzizttfLDsCbj.png" /></figure><p>Run it once and the token is stored in a collection variable:</p><pre>let response = JSON.parse(pm.response.text()); pm.collectionVariables.set(&quot;bearerToken&quot;, response.access_token);</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uyUujckkLpKMvbRK.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NrEyGf9wIZPCeT5C.png" /></figure><p>Every request in the collection uses the token variable automatically. When the token expires, you can simply run the token request again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_Tn5evpKZXR41CAl.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*p_Vww6a3eA9K-MJ9.png" /></figure><h4>Getting started</h4><p>You will need a Business Central environment, an Entra ID app registration, API permissions, and your tenant ID, client ID, and client secret. Import the collection, open the Variables tab, and enter your values. The collection is self contained, so there is no separate environment file to import.</p><h4>Finding a company</h4><p>Most Business Central endpoints are company specific, so one of the first things you will need is a company ID. The collection includes a List Companies request. Run it, copy the company ID you want to work with, and save it into the companyId variable. That is enough to get most requests working.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KYBNw_3GBqGHzve0.png" /></figure><h4>Why I use it</h4><p>I originally built this for my own use, but it ended up becoming my default starting point whenever I need to work with the Business Central API.</p><p>Instead of creating requests from scratch, I can import the collection, get a token, pick a company, and start testing.</p><h4>Try It</h4><p>Download the Postman collection: <a href="https://github.com/jeffreybulanadi/postman-api-v2">github.com/jeffreybulanadi | Business Central API v2.0 — Postman Collection</a></p><h4>Support for the Community</h4><p>If this collection helped you or saved you time, feel free to share it with others. Have feedback or questions? Leave a comment or send me a message.<br> Follow <a href="https://www.linkedin.com/in/jeffreybulanadi">Jeffrey Bulanadi</a> for more Business Central development content.</p><h4>Sources worth bookmarking</h4><p><em>Originally published at </em><a href="https://learnbeyondbc.com/blogs/postman-collection-business-central-api-v2"><em>https://learnbeyondbc.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb21df9fc8ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stop Rebuilding Postman Collections from Scratch. Use Raw URLs Instead.]]></title>
            <link>https://medium.com/@jeffreybulanadi/stop-rebuilding-postman-collections-from-scratch-use-raw-urls-instead-e6e1e199927d?source=rss-644f82ae8dc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6e1e199927d</guid>
            <category><![CDATA[dynamics-business-central]]></category>
            <category><![CDATA[d365-business-central]]></category>
            <category><![CDATA[msdyn365bc]]></category>
            <category><![CDATA[business-central]]></category>
            <dc:creator><![CDATA[Jeffrey Bulanadi]]></dc:creator>
            <pubDate>Mon, 06 Apr 2026 09:36:56 GMT</pubDate>
            <atom:updated>2026-04-06T09:36:56.308Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4gUzVfp2WmQqloi6s3zp5A.png" /></figure><p>A step-by-step guide to importing Postman collections from Azure DevOps and GitHub</p><p>Quick story on why I wrote this.</p><p>I got assigned to a handover project with a fair bit of API work. No API docs, no Postman collections, nothing. Just the AL project files.</p><p>So I built my own Postman collection from scratch. Then a second dev joined. They did the same. Then a third.</p><p>Everyone had their own copy. Nobody was in sync. Requests were slightly different across the team.</p><p>I feel like teams can do better here.</p><p><strong>The Simple Fix</strong></p><p>If your team stores collections in Azure DevOps or GitHub, there’s a simple way to share them through Postman and keep everyone on the same page.</p><p>I wrote a full step-by-step walkthrough covering:</p><p>✔️ <strong>How to export a Postman collection properly.<br></strong>Only properly exported Postman JSON files can be reliably imported later using Raw URLs.<br>✔️ <strong>How to structure your repo so it’s “Postman-import ready”.<br></strong>Postman doesn’t care if your repo is on GitHub or Azure DevOps. It only cares about the file itself and whether it’s accessible.<br>✔️ <strong>Import using Raw URLs from GitHub.<br></strong>This is the cleanest and fastest method. Click the Raw button, copy the URL, paste into Postman. Done.<br>✔️ <strong>Import by downloading the file.<br></strong>If raw URLs are restricted or you prefer working offline, download the file and drag it into Postman.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ig5r8fZOKZ3WZ_pqNTQlGw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B_mQ3RX9yA7zdobGIGPUaA.png" /></figure><p><strong>Part 1 of 3<br></strong>This is the first post in a 3-part series:<br>- <strong>**Part 1**</strong> (this one): Import using Raw URLs<br>- <strong>**Part 2**</strong>: Connecting GitHub directly to Postman<br>- <strong>**Part 3**</strong>: Full CI/CD automation with the Postman API</p><p>Read the full guide with screenshots:<br><a href="https://learnbeyondbc.com/blogs/using-raw-urls-to-import-postman-collections-azure-devops-github">Using Raw URLs to Import Postman Collections from Azure DevOps &amp; GitHub</a></p><p>How does your team handle sharing API collections? I’d love to hear what works for you.</p><p><em>*Follow me for more practical insights on Microsoft Dynamics 365 Business Central, AL development, and the surrounding ecosystem.*</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6e1e199927d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BC Docker Manager: The Easiest Way to Run Business Central Containers]]></title>
            <link>https://medium.com/@jeffreybulanadi/bc-docker-manager-the-easiest-way-to-run-business-central-containers-14105f0d6b36?source=rss-644f82ae8dc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/14105f0d6b36</guid>
            <category><![CDATA[msdyn365bc]]></category>
            <category><![CDATA[business-central]]></category>
            <category><![CDATA[d365-business-central]]></category>
            <category><![CDATA[dynamics-business-central]]></category>
            <dc:creator><![CDATA[Jeffrey Bulanadi]]></dc:creator>
            <pubDate>Mon, 06 Apr 2026 06:15:03 GMT</pubDate>
            <atom:updated>2026-04-06T06:15:03.867Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dKlE8d4xhV_DGx_yyIiR0g.png" /></figure><p>Why I built a VS Code extension to replace PowerShell scripts, Docker Desktop, and BcContainerHelper</p><p><strong>BC Docker Manager</strong></p><p>A VS Code extension that lets you create and manage BC Docker containers without PowerShell scripts, without Docker Desktop, and without BcContainerHelper.</p><p>Here’s what it can do:</p><p>✔️ <strong>Browse every BC version from the Microsoft CDN.</strong> <br>Switch between Sandbox and OnPrem, filter by country and major version, and create a container in three clicks.<br>✔️ <strong>Create containers in 3 clicks. <br></strong>The creation wizard walks you through container name, username, password, and EULA. Then it pulls the image, runs docker, waits for the health check, and configures networking for you.<br>✔️ <strong>Generate launch.json, compile, publish AL apps.</strong> <br>Connect the AL Language extension to your container instantly. Compile your AL project inside the container using alc.exe. No local compiler needed. Publish, sync, and install with one click.<br>✔️ <strong>One click environment setup.<br></strong>The extension checks if Hyper-V and Docker Engine are ready. If something is missing, click Setup Everything and it handles the rest.<br>✔️ <strong>Manage users, databases, networking, SSL.</strong> <br>Add BC users with permissions, create test users, backup and restore databases, update hosts file, and install SSL certificates.<br>✔️ <strong>Save container profiles for different projects.<br></strong>Save your container setup and reuse it anytime. Great for working with multiple clients or projects.</p><p><strong>Why now?</strong></p><p>Microsoft also announced that BcContainerHelper is being retired. So if you’re still relying on it, this is a good time to explore other options.</p><p>BC Docker Manager is free, MIT licensed, and open source.</p><p><strong>Try it out</strong></p><p>Read the full write up on my blog:<br><a href="https://learnbeyondbc.com/blogs/bc-docker-manager-easy-containers">https://learnbeyondbc.com/blogs/bc-docker-manager-easy-containers</a></p><p>Install from VS Code Marketplace:<br><a href="https://marketplace.visualstudio.com/items?itemName=jeffreybulanadi.bc-docker-manager">https://marketplace.visualstudio.com/items?itemName=jeffreybulanadi.bc-docker-manager</a></p><p>Source code on GitHub:<br><a href="https://github.com/jeffreybulanadi/bc-docker-manager">https://github.com/jeffreybulanadi/bc-docker-manager</a></p><p>If you’re still using that old PowerShell script, give it a try and let me know what you think. Feedback, issues, and PRs are all welcome.</p><p><em>*Follow me for more practical insights on Microsoft Dynamics 365 Business Central, AL development, and the surrounding ecosystem.*</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14105f0d6b36" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AL Indent Prism, a tiny VS Code extension that makes AL code reviews easier]]></title>
            <link>https://medium.com/@jeffreybulanadi/al-indent-prism-a-tiny-vs-code-extension-that-makes-al-code-reviews-easier-1d3473d4a358?source=rss-644f82ae8dc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d3473d4a358</guid>
            <category><![CDATA[business-central]]></category>
            <category><![CDATA[msdyn365bc]]></category>
            <dc:creator><![CDATA[Jeffrey Bulanadi]]></dc:creator>
            <pubDate>Sat, 20 Dec 2025 18:08:00 GMT</pubDate>
            <atom:updated>2025-12-20T18:08:53.543Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h-xobaGdPSN_hW35TbIPCA.png" /></figure><p>Sharing something that helped me during AL code reviews.</p><p>Before the holiday shutdown, I was reviewing some AL code with very deep nesting.</p><p>It was hard to follow, pretty common in BC projects as extensions grow.</p><p>To make structure easier to see, I wrote a small VS Code extension called <strong>AL Indent Prism</strong>.</p><p>It adds subtle background colors to each indent level so you can visually follow nesting without changing your code.</p><p><strong>Key points:</strong></p><ul><li>Works only on AL files</li><li>Supports light and dark themes</li><li>Does not modify code or formatting</li></ul><p>Full write-up: <a href="https://learnbeyondbc.com/blogs/al-indent-prism-code-review">See Your AL Code Structure Instantly with AL Indent Prism</a></p><p>Hope this helps other BC developers dealing with deep AL nesting. Feedback, issues, or pull requests are very welcome.</p><p>Does not modify code or formatting</p><p>Hope this helps other BC developers dealing with deep AL nesting. Feedback, issues, or pull requests are very welcome.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d3473d4a358" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How-To Update Global Apps in Business Central (a no BS guide)]]></title>
            <link>https://medium.com/@jeffreybulanadi/how-global-app-updates-actually-work-in-business-central-824e1bb5b3b3?source=rss-644f82ae8dc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/824e1bb5b3b3</guid>
            <category><![CDATA[business-central]]></category>
            <category><![CDATA[msdyn365bc]]></category>
            <dc:creator><![CDATA[Jeffrey Bulanadi]]></dc:creator>
            <pubDate>Sun, 14 Dec 2025 12:24:52 GMT</pubDate>
            <atom:updated>2025-12-14T12:25:17.025Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UD3fyyJKhtSbiCXZvOkS8Q.png" /></figure><p>Have you ever shipped an AppSource update, told the client to install it, then got the message:</p><p>Hey, I can’t see the changes.”</p><p>That happened to me recently.</p><p>The app was live. Validation passed. Other tenants had the update. But one client didn’t. Nothing was broken. The issue was simply how global app updates behave in Business Central when platform versions don’t align.</p><p>That experience pushed me to write a short, practical guide on how to update global apps properly using the Business Central Admin Center.</p><p>This article walks through what’s really happening behind the scenes and how to avoid the same confusion in future releases.</p><p>Read the full guide here: <a href="https://learnbeyondbc.com/blogs/update-global-app-business-central">https://learnbeyondbc.com/blogs/update-global-app-business-central</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=824e1bb5b3b3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Surviving Dynamics Business Central Breaking Changes using AL Preprocessor directives]]></title>
            <link>https://medium.com/@jeffreybulanadi/surviving-dynamics-business-central-breaking-changes-using-al-preprocessor-directives-a0d315feea51?source=rss-644f82ae8dc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/a0d315feea51</guid>
            <category><![CDATA[msdyn365bc]]></category>
            <category><![CDATA[business-central]]></category>
            <dc:creator><![CDATA[Jeffrey Bulanadi]]></dc:creator>
            <pubDate>Tue, 02 Dec 2025 14:27:34 GMT</pubDate>
            <atom:updated>2025-12-02T14:27:34.200Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PMO69LkF99sgMzfa1va3EA.png" /></figure><p>Preprocessor directives in AL: a practical, no BS guide</p><p>Yo BC Artisans,</p><p>For the past few weeks there’s been a lot happening in the BC space. I remember Microsoft holding back the BC27 platform upgrade for a while, and I believe one of the reasons was breaking changes.</p><p>Here’s the thing: Platform 26.5 is the last stable update before 27.0.</p><p>26.5 had a bunch of changes, but nothing broke. e.g. Invoice Post. Buffer posting routine, No. Series, and other events.</p><p>Instead of being removed or marked obsolete, they just stopped firing, which breaks stuff if you’re subscribed to them.</p><p>Normally, Microsoft would notify you that your environment can’t be upgraded because of some extension you need to fix. But that didn’t happen in 26.x. So if you added a custom field in G/L entry and subscribed to an event that fills that field, and that event no longer fires then yeah, we’ve got a problem.</p><p>Good news though: those issues are now officially treated as breaking changes in BC platform upgrade 27.</p><p>Why am I telling you this?</p><p>Because I want to share how you can handle these changes, breaking or not, in a smarter way. Microsoft does it too (try to notice their pattern), but we often ignore it. I used to, honestly.</p><p>If you’ve been writing AL for BC long enough, you’ll eventually need to ship the same app to slightly different worlds: production vs sandbox, feature on vs off, or old runtime vs new runtime.</p><p>So how do you deal with that?</p><p>Meet <strong>Preprocessor directives</strong>. They’re underrated, not really popular among AL devs, probably because most haven’t seen them in action.</p><h4>TL;DR for beginners</h4><ul><li>Preprocessor directives are simple on/off switches at compile time.</li><li>You turn them on with names (called symbols) in app.json.</li><li>Use them for three things:</li><li>#if: include or exclude code.</li><li>#region: fold code for readability.</li><li>#pragma: temporarily hide a warning you already know about.</li><li>You choose the symbol names. Microsoft often uses CLEANXX e.g. CLEAN26, CLEAN27, and CLEANSCHEMA26 to control cleanup across versions.</li></ul><p>If you only remember one thing: put a symbol in app.json, then wrap code with #if SYMBOL_NAME and #endif</p><h4>What Preprocessor Directives Are</h4><p>If you’ve ever seen AL code with lines that start with #, you’ve met preprocessor directives. They’re not real code that runs in your app, think of it as giving special notes to the compiler so it can set things up before looking at your real program code.</p><p>In simple terms: A preprocessor directive is like telling the compiler:</p><p>&quot;Hey, before you start building the program, do this first.&quot;</p><p>Think of them like little switches or notes you leave for the compiler. They help you:</p><p>Pretty handy, right? But there are a few things to know so you don’t run into surprises:</p><ul><li>AL doesn’t give you built-in symbols like C#’s DEBUG.<br> You must<strong>create your own symbols</strong>.</li><li>Symbols are super simple: they’re either <strong>defined (true)</strong> or <strong>not defined (false)</strong>.<br> No values, no data, nothing fancy.</li><li>You can define symbols <strong>globally</strong> in app.json or <strong>locally</strong> in a file using #define and #undef.</li><li>Regions and #if blocks can be inside each other, but they <strong>can&#39;t overlap in weird ways</strong>. They need to stay properly nested.</li><li>And one important detail: <strong>user personalization and profiles do NOT use directives</strong>. These directives only work at compile time, not afterwards.</li></ul><p>That’s really all there is to it. Preprocessor directives don’t change how users experience your app; they just help you control and clean up your code before it ever gets compiled.</p><h4>Quick setup: define symbols (3 steps)</h4><p>Think of a symbol as a simple flag you turn on. If it is listed in app.json, it is true everywhere. If not, it is false.</p><ol><li>Add the symbol name to preprocessorSymbols in app.json.</li><li>Wrap code with #if SYMBOL and #endif.</li><li>Build. If the symbol is present, the code compiles. If not, the code is skipped.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*W91MepNSlpVm7GW-.png" /></figure><h4>Core building blocks (fast version)</h4><p>Conditional: skip (Reference from actual Microsoft code)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3-x-gXr2GHfb0wOv.png" /></figure><p>Remember:</p><p>Regions: fold code (Reference from MS)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ryjTb8tfm27FXU1o.png" /></figure><p>Only for navigation. Does not affect compilation.</p><p>Pragmas: silence a warning briefly (Another reference from MS)</p><p>Use when you know a warning, accept it for now, and will fix later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4Zm-hMToQWve0jRk.png" /></figure><p>Rules:</p><ul><li>Make the disabled block tiny.</li><li>Always restore.</li><li>Target only one warning code.</li></ul><p>Tiny pattern: disable → place the few lines → restore. Don’t wrap the whole file.</p><p>#pragma warning , a simple way to see it</p><p>Think of the <strong>compiler like a smoke alarm in your kitchen</strong>. When it detects smoke, <strong>it goes beep beep beep!, that’s a warning.</strong></p><p>But sometimes you’re just making a fried rice, a toast or whatever you are cooking, and you know it’s fine. You don’t want the alarm screaming while you finish cooking.</p><p>So you press the silence button:</p><p>That’s#pragma warning disable → &quot;Stop beeping for this warning right now.&quot;</p><p>Later, you let the alarm go back to normal: That&#39;s#pragma warning restore → &quot;Okay, beep again if you detect smoke.&quot;</p><p>Code example</p><pre>#pragma warning disable AL0468 // Silence this warning // Code where the warning is ignored #pragma warning restore AL0468 // Let warnings work again</pre><p>In short:</p><ul><li>Disable = mute the alarm for a specific warning.</li><li>Restore = unmute it so you don’t miss real problems.</li></ul><h4>Demo: Handling NoSeriesManagement → “No. Series” breaking change</h4><p>This is grab code from my actual repo (of course, I stripped out the sensitive stuff).</p><p>So here’s one of the big ones: Microsoft split and modernized number series starting in BC24 with the new Business Foundation module.</p><p>The old NoSeriesManagement codeunit is on its way out. If you&#39;re on BC27, it&#39;s gone.</p><p>The replacement codeunit is&quot;No. Series&quot; and &quot;No. Series - Batch&quot; if you&#39;re pulling lots of numbers at once.</p><p>How to survive it (2 quick steps):</p><p>Say you’ve got a data entry codeunit that needs numbers. Before, you’d call NoSeriesManagement. Now it’s swapped out for No. Series.</p><ol><li>Build a small wrapper codeunit (the “bridge”) with #if CLEAN26 inside.<br> That way, the bridge decides whether to call the old NoSeriesManagement or the new No. Series depending on your target version.</li><li>Flip the switch in app.json when you&#39;re ready for BC27.<br> Just add&quot;CLEAN26&quot; to preprocessorSymbols so the compiler uses the new path everywhere.</li></ol><p><strong>Usage:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zaxFjzi7Jy2khMA3.png" /></figure><h4>Demo: Invoice Posting Buffer change (“Invoice Post. Buffer” → “Invoice Posting Buffer”)</h4><p>Here’s another real sample from my repo.</p><p>We’re adding a custom field to G/L Entry and also to Invoice Post. Buffer.</p><p>Since Invoice Post. Buffer is being deprecated, we need to add the same field to the new table Invoice Posting Buffer as well.</p><p>This one changed around BC26.</p><p>The old table Invoice Post. Buffer got replaced by the new Invoice Posting Buffer.</p><p>Stuff that used to run as events on the table was moved into separate codeunits.</p><p>If you want your code to work on both versions, just put#if / #else around your calls.</p><p>Upgrade path in 2 steps:</p><ul><li>Add CLEAN26 in app.json when targeting the new buffer.</li><li>Subscribe to the new events only when CLEAN26 is defined; otherwise keep the legacy path.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*H9zWsGmTpMgHdZ5z.png" /></figure><h4>Versioned cleanup with CLEANxx and CLEANSCHEMAxx</h4><p>Microsoft’s Base App uses versioned symbols like CLEAN26, CLEAN27 and CLEANSCHEMA26 to control when obsolete code turns into removed code, and when schema can be dropped.</p><p>AL does not define these automatically. You choose when they are active by adding them to your app.json or CI build config.</p><p>i.e, keep a field until schema cleanup in 26</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*J56LUps0-AFt04J3.png" /></figure><h4>Gotchas (stuff I learned the hard way)</h4><ul><li>AL doesn’t give you any built‑in symbols. If you need one, define it yourself.</li><li>You can’t overlap regions with #if blocks. If you need both, just nest them.</li><li>If you #pragma warning disable and don&#39;t restore it, it stays off until the end of the file. Keep that scope tight.</li><li>Directives only work at compile time. They won’t change at runtime based on tenant or environment.</li></ul><h4>Pocket reference</h4><h4>FAQ (quick answers)</h4><ul><li>Do symbols turn on automatically when I upgrade? No. You must add them to app.json or set them in your build.</li><li>Can I give symbols values? No. A symbol is either defined (true) or not (false).</li><li>Is #region only for looks? Yes. It does not change the compiled code.</li><li>Is it safe to disable warnings? Only if you scope it to the smallest possible place and restore it after.</li></ul><h4>Final thoughts</h4><ul><li>You can run your code in many versions, just use #if to handle the differences.</li><li>Copy Microsoft’s style for symbols, like CLEAN26 or CLEAN27. Simple names are fine.</li><li>Think of #pragma warning like a smoke alarm. You can mute it or unmute it, but only for a short time. Always know what you&#39;re doing when you switch it off.</li></ul><h4>Support for the Community</h4><p>I really appreciate any comments, good or bad. That’s how we learn from each other, right?</p><p>Drop a note and you’ll definitely keep me smiling. LOL, seriously, thank you.</p><p>If sharing this doesn’t take much of your time, I’d be grateful. It helps spread the knowledge and keep the love going for the <a href="https://www.linkedin.com/company/microsoft-dynamics-365-community">Microsoft Dynamics 365 Community</a>.</p><p>And if you want to see more stuff I post beyond Business Central, give me a follow: <a href="https://www.linkedin.com/in/jeffreybulanadi">Jeffrey Bulanadi</a></p><h4>Demo Repository</h4><p>All the code and screenshots are up on my GitHub.</p><p>Check it out here: <a href="https://github.com/jeffreybulanadi/BCSaturdayCodeHacks/tree/main/hacks/2025-11-29-PreprocessorDirectives">How to survive breaking changes using Preprocessor directives in AL</a></p><h4>Sources worth bookmarking</h4><p><em>Originally published at </em><a href="http://learnbeyondbc.com/blogs/bc-breaking-changes-al-preprocessor"><em>http://learnbeyondbc.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0d315feea51" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Real talk: extensions.json is the BC dev file nobody talks about, but everyone should use.]]></title>
            <link>https://medium.com/@jeffreybulanadi/real-talk-extensions-json-is-the-bc-dev-file-nobody-talks-about-but-everyone-should-use-bed34e689d6c?source=rss-644f82ae8dc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/bed34e689d6c</guid>
            <category><![CDATA[business-central]]></category>
            <category><![CDATA[msdyn365bc]]></category>
            <dc:creator><![CDATA[Jeffrey Bulanadi]]></dc:creator>
            <pubDate>Sun, 16 Nov 2025 02:17:07 GMT</pubDate>
            <atom:updated>2025-11-16T02:17:07.742Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IqWraEpi2emB8CdPUBYu7A.jpeg" /></figure><p>Picture this: New dev joins your team. “What VS Code extensions do I need?” You list them. They install most. Miss some. Wrong versions. Things break. You troubleshoot.</p><p>Sound familiar? This file eliminates that forever.</p><p>✅ Auto-installs extensions <br>✅ Keeps setups identical <br>✅ 20+ essential tools explained <br>✅ Translation tools for multilingual projects <br>✅ Step-by-step guide to build your own <br>✅ Full walkthrough with working code</p><p>📖 Read the full guide 👉 <a href="https://learnbeyondbc.com/blogs/extension-json-al-configuration-file-bc-developers">https://learnbeyondbc.com/blogs/extension-json-al-configuration-file-bc-developers</a></p><p>#BCWeekendCodeHacks #msdyn365BC #BusinessCentral #ALDevelopment #LearnBeyondBC</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bed34e689d6c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microsoft just updated their official guide for running container-based development environments in…]]></title>
            <link>https://medium.com/@jeffreybulanadi/microsoft-just-updated-their-official-guide-for-running-container-based-development-environments-8e2339219cd4?source=rss-644f82ae8dc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e2339219cd4</guid>
            <category><![CDATA[msdyn365bc]]></category>
            <category><![CDATA[business-central]]></category>
            <dc:creator><![CDATA[Jeffrey Bulanadi]]></dc:creator>
            <pubDate>Thu, 06 Nov 2025 15:54:42 GMT</pubDate>
            <atom:updated>2025-11-06T15:55:09.356Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9misA4Rk5rFpmGsgTn8FAg.png" /></figure><p>Microsoft just updated their official guide for running container-based development environments in Dynamics 365 Business Central.</p><p>If you’re using Docker + BCContainerHelper, this refresh includes:</p><p>✔️ Updated install steps<br>✔️ Insider build access via artifact URLs<br>✔️ Troubleshooting tips for memory, disk, and browser issues<br>✔️ PowerShell examples for publishing apps</p><p>📌 Read the updated guide: <br><a href="https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-running-container-development">https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-running-container-development</a></p><p>#BusinessCentral #msdyn365BC</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e2339219cd4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microsoft Tightens Code Signing Rules for Business Central Developers]]></title>
            <link>https://medium.com/@jeffreybulanadi/microsoft-tightens-code-signing-rules-for-business-central-developers-5a8721f60bec?source=rss-644f82ae8dc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a8721f60bec</guid>
            <category><![CDATA[d365-business-central]]></category>
            <category><![CDATA[msdyn365bc]]></category>
            <category><![CDATA[business-central]]></category>
            <dc:creator><![CDATA[Jeffrey Bulanadi]]></dc:creator>
            <pubDate>Wed, 05 Nov 2025 00:48:14 GMT</pubDate>
            <atom:updated>2025-11-05T00:48:14.575Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jS7LzaxELuCigJaFEolTiA.png" /></figure><p>If you’re publishing .app files for #msdyn365BC, take note: Microsoft now requires secure hardware (Azure Key Vault or FIPS USB) for newer certificates. Unsigned extensions won’t pass, AppSource or on-prem.</p><p><strong>Signing options:</strong></p><p>✔️ Azure Key Vault (recommended) <br>✔️ .PFX file (legacy only) <br>✔️ Self-signed (local/on-prem only)</p><p>Whether you’re shipping to AppSource or deploying internally, make sure your signing setup is compliant.</p><p>Full guide: 👉 <a href="https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-sign-extension">Sign an app package file — Business Central | Microsoft Learn</a></p><p>#msdyn365BC #BusinessCentral #ALDevelopment #DataArchive</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a8721f60bec" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>