Code Compass

Introduction A Security Group is a way to group users together so that you can give access to all of them at once. For example, if everyone in the Finance team needs access to certain files or apps, you can add them to a group and give the group permission instead of doing it for each person. In Office365, Security Groups are managed through Azure Active Directory, which handles sign-ins and user identities in Microsoft 365.  They help IT teams save time, stay organized, and keep company data safe. The same Security Groups you create in Azure Active Directory (AAD) can also be used in Dynamics 365 Business Central to manage user permissions. Instead of giving access to each user one by one in Business Central, you can connect a Security Group to a set of permissions. Then, anyone added to that group in Azure AD will automatically get the same permissions in Business Central. They’re also helpful when you want to control environment-level access, especially if your company uses diff...

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 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 look at how to set up notifications directly within Business Central.  References MS Learn - Get in-product notifications about issues with job queue background processing MS Learn - Job Queue Configuration Search for "Assisted Setup" in Business Central's glob...

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...