Code Compass

Introduction In today’s fast-moving world of software development, Continuous Integration (CI) and Continuous Deployment (CD) are key to building and releasing updates quickly and reliably. For Business Central developers, AL-Go for GitHub makes this process easy by using GitHub Actions to automate builds, testing, and deployments. It comes with ready-to-use templates that help you set up a complete CI/CD pipeline in minutes so you can focus more on coding and less on managing workflows. Each build typically takes around 20 minutes when using containers, which fits comfortably within GitHub’s free limits for most projects 2,000 minutes per month for private repositories on the Free tier, 3,000 minutes on the Team tier, and up to 50,000 minutes on the Enterprise tier. Since public repositories get unlimited free minutes, AL-Go for GitHub offers an affordable and powerful way to maintain professional DevOps practices without extra costs. Overall, it’s a simple, cost-efficient, and deve...

Introduction When working on big projects, it can be hard to quickly find classes, methods, or properties spread across different libraries. Searching through files one by one takes too much time. This is where metadata search in Visual Studio helps. It lets you explore and navigate types from external libraries (like .NET assemblies or NuGet packages) even if you don’t have the source code. Visual Studio creates a readable view of the compiled metadata, so you can instantly see definitions and details, almost like built-in documentation. References Metadata search - Visual Studio Usage In Visual Studio, go to Dynamics 365 > Metadata Search  OR  Ctrl + R, Ctrl + S . Start typing the name of the element you are looking for. Results appear as you type. Double-click a result to go directly to that metadata or code. You can also right-click to add items to your project. You can filter via the follow criteria: Name : Search by element name (default).  Type : Limit by type, ...

Introduction A job queue lets users set up and manage background tasks that run automatically.  These tasks can be scheduled to run on a recurring schedule. For a long time, users had a common problem in Business Central—when a job queue failed, there was no alert or warning. You’d only notice something was wrong when a regular task didn’t run for a few days. Some people tried to fix this by setting up another job queue to watch and restart failed ones. But that didn’t always work, especially if an update happened at the same time. Now, Microsoft has finally added a built-in way to get alerts when a job queue fails.  You can get notified either inside Business Central or by using Business Events. In this blog, we'll see the process of leveraging the Business Events to set up notifications on job queue statuses. References MS Learn - Get in-product notifications about issues with job queue background processing MS Learn - Job Queue Configuration Search for "Assisted Setup"...

Introduction One of our clients had made some small mistakes while providing the data for their opening balances, which caused the item costs to be wrong. After a lot of back-and-forth, we finally got a list of 100+ items with the correct costs. We thought it would be easy to fix using Edit in Excel but then we ran into an error: "Quantity must have a value in Item Journal Line." But this is odd as when we are creating the entries manually, we don't need to set the Quantity from anywhere. In fact, the Quantity field isn't even editable, it is populated when the "Applies-to Entry" field is updated. We tried using Configuration Package.. same thing! We tried to create an excel import, that uploads data in the journal.. same thing! So what's going on? Details After a bit of debugging we found this piece of code to be the problem -  And this -> When you update the "Unit Cost (Revalued)" field in Business Central, it also updates the "Invent...

Introduction An AI agent is a smart program that can think, make decisions, and do tasks. Sometimes it works alone, and sometimes it works with people or other agents. The main difference between an agent and a regular assistant is that agents can do things on their own. They don’t just help—you can give them a goal, and they’ll try to reach it. Every AI agent has three main parts: Model : This is the brain that helps the agent understand language and think. Instructions : These tell the agent what it should do and what rules to follow. Tools : These help the agent find information or take action. Agents can take input like a message or a prompt and respond with answers or actions.  For example, they might look something up or start a process based on what you asked. Azure AI Foundry is a platform that brings all these things together; so you can build, train, and manage AI agents easily. References What is Azure AI Foundry Agent Service? - Azure AI Foundry | Microsoft Learn Unders...