Predicting the Demand: Automating Demand Forecasting in Dynamics 365 Business Central Using Azure Logic Apps, Data Lake, and Databricks Summary Knowing how many products to keep in warehouses is tough for manufacturers and distributors. During busy seasons, customer orders can jump 10 times higher than normal. When teams rely on manual spreadsheets, they often run out of products or buy too much and run out of storage space. This article explains a simple, automated solution built with Microsoft Dynamics 365 Business Central, Microsoft Azure, and Azure Databricks. Table of Contents The Problem: Swings in Customer Demand The 5-Step Solution Overview How Data is Collected and Cleaned (Medallion) How the Prophet Forecasting Model Works Clear Decision-Making with Forecasted Metrics Real Benefits for Businesses Frequently Asked Questions What You Will Learn Why manual spreadsheets and static inventory numbers fail when demand spikes. How Azure Logic Apps fetches data from Business Central automatically by using scheduled triggers. How raw records are organized into Bronze, Silver, and Gold layers. How the Prophet model forecasts demand using yearly trends and weekly patterns. How dynamic safety stock gives purchasing teams clear replenishment recommendations. 1. The Problem: Swings in Customer Demand Most manufacturers and distributors face a big challenge: customer demand is not steady throughout the year. Some months are quiet, while other months bring huge surges in orders. Season Months Demand Level What Happens Peak Busy Season June – August 8x – 10x Surge Huge spike in customer orders. Suppliers take longer to deliver, risking major stockouts. Mid-Year Rush January 3x – 4x Normal Quick wave of replacement orders and new account setups. Spring Planning March – May 2x Normal Customers use annual budgets to place advance orders for summer projects. Regular Season Off-Peak Months 1x Baseline Standard, steady daily orders. Why Traditional Methods Fail: Static Rules: Standard ERP rules use fixed inventory numbers all year. These are too small for busy seasons (causing stockouts) and too large for slow seasons (wasting money). Longer Supplier Delays: When everyone orders at once during peak seasons, suppliers take weeks longer to deliver parts. Full Warehouses: Storing large boxes during slow months takes up valuable warehouse space and ties up cash. Manual Spreadsheet Errors: Planning teams spend hours copying and pasting data into Excel spreadsheets without automated forecasting tools. “You don’t need to replace your ERP system. By adding automated cloud forecasting with Azure and Databricks to Dynamics 365 Business Central, past sales history turns into clear, actionable purchasing foresight.” 2. The 5-Step Solution Overview To solve this, we created an automated pipeline that connects daily ERP transactions to cloud forecasting and delivers clear inventory planning targets. How the Automated Flow Works 1 Dynamics 365 Business Central Holds daily sales, purchases, items, and warehouse records. ↓ 2 Azure Logic Apps (Scheduled Ingestion) Fetches data from Business Central automatically by using scheduled triggers without slowing down the ERP system. ↓ 3 Azure Data Lake (Cloud Storage) Stores all historical files securely in one central place. ↓ 4 Azure Databricks (Prophet Model) Cleans the data, runs Prophet forecasting models, and calculates the forecasted buffer stock needed for every item. ↓ 5 Visual Reports in Power BI Forecasted demand and recommended safety stock are displayed in Power BI reports for clear decision-making. 3. How Data is Cleaned & Organized (Bronze, Silver, Gold) In Azure Databricks, data moves through three simple stages known as the Medallion Architecture: Bronze Layer Raw Data Stores exact copies of daily files directly from Business Central (sales, purchases, items, warehouses). Keeps a complete, untouched history so nothing is ever lost. Silver Layer Cleaned Data Fixes missing dates, removes duplicates, and standardizes item numbers across all warehouses. Separates real customer orders from internal warehouse transfers. Gold Layer Forecasting Results Combines daily sales into clear trends and calculates forecasted stock targets for each product. Ready to feed interactive Power BI reports for planners and stakeholders. 4. How the Prophet Forecasting Model Works The Prophet forecasting model analyzes four key factors from past sales: The 3 Things the Model Learns: Overall Growth: Is customer demand growing year over year? Yearly Seasons: Which months have huge order spikes, and which months are quiet? Weekly Patterns: Do customers place most orders on weekdays compared to weekends? By combining these patterns, the system calculates the recommended safety stock for every item and warehouse: Forecasted Safety Stock: The recommended buffer quantity to keep on hand to protect against unexpected surges or supplier delivery delays. 5. Clear Decision-Making with Forecasted Metrics Instead of relying on guesswork in disconnected spreadsheets, supply chain planners have clear, data-driven targets calculated by Azure Databricks. These forecasted metrics give purchasing and warehouse managers actionable recommendations: Projected Demand: Forward-looking estimates of how many units customers will need in upcoming months. Early Order Timing: Clear signals on when to order from suppliers before peak seasons begin. Warehouse Stock Balancing: Guidance on how much inventory to position across regional warehouse hubs. 6. Real Benefits for Manufacturers Order 6–8 Weeks Ahead Purchasing teams get early warnings before big busy seasons, allowing them to book orders before supplier queues fill up. Balanced Warehouses Items are placed in the right regional warehouses closest to where customers will buy them. More Warehouse Space Bulky products arrive only when needed, keeping aisles clear and reducing expensive storage costs. Data-Driven Planning No more spending days building complicated formulas in Excel. Machine learning provides reliable demand curves and inventory targets. 7. Frequently Asked Questions (FAQ) 1 Will this slow down Business Central for daily users? No. Data is copied automatically during quiet nighttime hours into Azure. All calculations happen in the cloud, so Business Central stays fast and responsive for everyday business. 2 Why use the Prophet model instead of standard ERP reorder rules? Standard ERP rules use one fixed number for the entire year. The Prophet model automatically adapts to upcoming seasons, supplier lead times, and sales trends. 3 How do planning teams use these calculated metrics? Planning and purchasing teams access these forecasted metrics directly through interactive Power … Continue reading Predicting the Demand: Automating Demand Forecasting in Dynamics 365 Business Central Using Azure Logic Apps, Data Lake, and Databricks →

Summary For Emirates Consortium, we designed a customized Department Budget Management solution in Microsoft Dynamics 365 Business Central to bring greater control and visibility to departmental budgeting. The solution enables Finance teams to maintain budgets by Department, Budget Year, Budget Month, Category, and Subcategory while separately tracking Original Budget, Additional Budget, Effective Budget, Consumed Amount, and Available Budget. It also introduces controlled budget revisions, Purchase Order validation, Finance-only access, revision history, and consumption tracking based on posted purchasing transactions. Table of Contents Introduction The Business Requirement Designing the Department Budget Structure What Finance Can See on the Department Budget Setup Separating Original, Additional and Effective Budget Protecting the Original Budget Controlled Budget Revision Why the Revision Is Linked to a Purchase Order Purchase Order Must Be Open Before Budget Revision Restricting Budget Revision to Finance Maintaining Budget Revision History How We Calculate the Available Budget Calculating the Consumed Amount from Posted Transactions How Partial Invoicing Is Handled Putting It All Together Business Benefits Conclusion Introduction As part of our implementation for Emirates Consortium, we designed a customized Department Budget Management solution in Microsoft Dynamics 365 Business Central to strengthen budget control and provide Finance teams with greater visibility into departmental expenditure. The solution enables budgets to be maintained using a structured combination of Department, Budget Year, Budget Month, Category, and Subcategory. It also provides separate visibility into the Original Budget, Additional Budget, Effective Budget, Consumed Amount, and Available Budget, along with controlled budget revisions, Purchase Order validation, Finance-specific access, revision history, and consumption tracking based on posted purchasing transactions. This approach was designed to help Finance teams answer important budget-control questions such as: What was the original approved budget? How much additional budget was provided later? How much has already been consumed? How much budget is currently available? Who revised the budget and when? Why was additional budget required? For one of our Business Central implementations, we addressed this requirement by developing a dedicated Department Budget Management solution. The objective was to keep the process simple for Finance users while providing the controls and auditability expected from an ERP system. The Business Requirement Previously, departmental budgets were maintained outside Business Central, making it difficult to validate purchasing transactions against the latest available budget. Another challenge was that a department could have several different budgets. Department Year Month Category Subcategory Original Budget ADMIN 2026 August OPEX Fuel Cost 5,000 ADMIN 2026 August OPEX Engine 5,000 ADMIN 2026 August CAPEX Boat 50,000 Therefore, maintaining only a single budget amount against a department was not sufficient. We needed a structure that could identify the exact budget applicable to a particular expenditure. Designing the Department Budget Structure We created a dedicated Department Budget Setup page in Business Central. Each budget is uniquely identified using the following combination: Department + Budget Year + Budget Month + Category + Subcategory For example: ADMIN → 2026 → August → OPEX → Fuel Cost This structure allows Finance to maintain separate budgets for different expense areas within the same department and month. From a technical perspective, the same combination is used as the primary key of the Department Budget Setup table: key(PK; “Department Code”, “Budget Year”, “Budget Month”, Category, Subcategory) { Clustered = true; } This ensures that duplicate budget records cannot be created for the same combination. What Finance Can See on the Department Budget Setup The Department Budget Setup page was designed to give Finance a quick view of the complete budget position. Field Purpose Department Code Department for which the budget is maintained Purchase Order No. Related Purchase Order, where applicable Budget Year Budget year Budget Month Month for which the budget is maintained Category Expense classification, such as OPEX or CAPEX Subcategory Detailed expense classification Original Budget Amount Initial budget allocated by Finance Additional Budget Amount Additional budget provided through revisions Effective Budget Amount Total approved budget after revisions Consumed Amount Budget already utilized Available Budget Amount Remaining budget available for utilization Last Revised By User who last revised the budget Last Revised Date Time Date and time of the latest revision This gives Finance a consolidated view without having to calculate the current budget manually. Example Original Budget Amount: 5,000 Additional Budget Amount: 10,000 Effective Budget Amount: 15,000 Consumed Amount: 5,400 Available Budget Amount: 9,600 From a single page, Finance can immediately understand the complete position of that budget. Separating Original, Additional and Effective Budget One of the most important decisions in this solution was not allowing the original budget to be overwritten whenever additional funds were approved. Consider an original budget of: AED 10,000 Later, Finance approves an additional: AED 5,000 Simply changing the original budget from 10,000 to 15,000 would remove the history of what was initially approved. Instead, we maintain these amounts separately: Budget Component Amount Original Budget 10,000 Additional Budget 5,000 Effective Budget 15,000 The calculation is: Effective Budget = Original Budget + Additional Budget “Effective Budget Amount” := “Budget Amount” + “Revised Budget Amount”; Although the calculation itself is straightforward, keeping these values separate provides much better financial visibility and auditability. Protecting the Original Budget Once a Department Budget is created, the original budget and its identifying information should not be casually changed. For this reason, we added validations to protect fields such as: Department Budget Year Budget Month Category Subcategory Original Budget Amount if “Budget Amount” <> xRec.”Budget Amount” then Error( ‘The original budget amount cannot be changed after the budget is created. Use the Revise Budget action instead.’); Therefore, instead of allowing: Create Budget → Manually Edit Budget → Edit Again the controlled process becomes: Create Original Budget → Lock Original Amount → Use Revise Budget for Additional Allocation This preserves the integrity of the original budget. Controlled Budget Revision Budgets naturally change during the year, so preventing all changes would not be practical. To handle this requirement, we introduced a dedicated Revise Budget action. When additional budget is required, the Finance user provides: Purchase Order No. Revision Amount Revision Reason Description Amount Original Budget … Continue reading How an Abu Dhabi-Based Diversified Holding Company Built Department-Wise Budget Control in Microsoft Dynamics 365 Business Central →

Summary This article explores how Emirates Consortium LLC expanded its use of Microsoft Dynamics 365 Business Central beyond finance to establish a more structured procurement process. Previously, budgets were managed manually through Excel and some procurement activities were performed outside the ERP. The implemented solution introduced a customized Purchase Request-to-Purchase Order process covering the initial requirement, approval, vendor and item selection, Purchase Quotes, Purchase Orders, and budget validation. The process also carries important procurement information such as Department, Category, Subcategory, Location, and Dimensions throughout the purchasing cycle, creating greater visibility, control, and traceability. Table of Contents Introduction From Finance-Only Usage to Broader Business Central Adoption Starting Procurement with a Purchase Request Keeping Supporting Documents with the Request Approval Before Procurement Moves Forward Turning an Approved Request into Purchase Quotes One Purchase Request Can Become Multiple Purchase Quotes Carrying Information Forward From Purchase Quote to Purchase Order Bringing Budget Visibility into the Purchase Order The Bigger Picture Conclusion 1. Introduction For many organizations, procurement doesn’t begin with a Purchase Order. It begins much earlier—with a business user identifying a requirement, requesting approval, obtaining quotations, selecting suppliers, and ensuring that the purchase is properly categorized and authorized. When these steps happen outside the ERP, organizations can end up relying on spreadsheets, emails, manual approvals, and disconnected procurement activities. This makes it difficult to maintain a consistent process and creates additional effort for both procurement and finance teams. This was the challenge addressed for Emirates Consortium LLC. Emirates Consortium had been a long-standing client and had primarily been using the Finance capabilities of Microsoft Dynamics 365 Business Central. As part of its next stage of ERP adoption, the organization wanted to expand its use of Business Central and bring more of its procurement activities into the system. One of the key areas was procurement and budget control. Previously, budgets were being managed manually through Excel, while some procurement activities were being performed outside the ERP. The objective was therefore not simply to introduce Purchase Orders into Business Central, but to establish a more structured procurement process—from the initial purchase requirement through approval, supplier selection, quotation, and Purchase Order creation. The Implemented Solution The resulting solution introduced a customized Purchase Request-to-Purchase Order process within Business Central, with approval controls and budget information carried throughout the purchasing cycle. 2. From Finance-Only Usage to Broader Business Central Adoption Emirates Consortium’s journey is an example of how an organization can progressively expand its use of Business Central. Rather than limiting Business Central to financial transactions, the implementation extends the platform into operational procurement. The process starts with a Purchase Request, which becomes the starting point for the procurement lifecycle. Procurement Process Flow Purchase Request → Approval → Vendor & Item Selection → Purchase Quote → Purchase Order → Budget Validation → PO Approval This approach brings the procurement process into the same ERP environment that already supports the organization’s financial operations. The implementation specifically carries important procurement classification information—such as Department, Category, Subcategory, Location, and Dimensions—through the process so that it can subsequently participate in budget validation. 3. Starting Procurement with a Purchase Request The first step in the process is the creation of a Purchase Request. Instead of starting directly with a Purchase Order, the requester first communicates what the business needs. The Purchase Request captures information such as: Department Category Subcategory Location Item or service required Quantity Unit of Measure Remarks Supporting documents For item-based requests, users can also check Item Availability before determining the quantity that needs to be purchased. A Clear Separation of Responsibilities The process creates an important separation between: “What does the business need?” and “Which supplier should we purchase it from?” That distinction is particularly useful in organizations where a requester may not be responsible for supplier selection. 4. Keeping Supporting Documents with the Request Procurement requests often require supporting information. For example, a requester may need to provide specifications, internal documentation, requirement details, or other reference material. The implemented process provides an Attachments option on the Purchase Request. Importantly, these attachments remain associated with the individual Purchase Request. They are not automatically transferred to the subsequent Purchase Quote or Purchase Order. Two Types of Supporting Information Documents supporting the original request. Documents supporting later purchasing or budget decisions. This distinction becomes particularly important in the over-budget scenario discussed in Part 2. 5. Approval Before Procurement Moves Forward Once the Purchase Request has been created, it cannot simply move directly into purchasing. The requester submits it using Send Approval Request. A dedicated Purchase Request approval workflow was configured for the process. The workflow supports: Approval Rejection Cancellation Delegation Approval notifications The Purchase Request progresses through statuses such as: Approval Status Flow Open → Pending Approval → Approved / Rejected Only after the required approval is completed can the request proceed to the quotation stage. This provides a controlled starting point for procurement. The organization doesn’t simply record what was purchased; it also records who requested it and who approved the requirement. 6. Turning an Approved Request into Purchase Quotes Once the Purchase Request has been approved, the next step is supplier sourcing. The implementation allows users to create a Purchase Quote directly from the approved Purchase Request. When the user selects Create Purchase Quote, Business Central opens a Vendor and Item Selection page based on the Purchase Request lines. This is particularly useful when a single request contains multiple items that may be sourced from different vendors. 7. One Purchase Request Can Become Multiple Purchase Quotes Consider a simple example. Purchase Request Line Selected Vendor Result Item A Vendor 1 Purchase Quote – Vendor 1 Item B Vendor 1 Purchase Quote – Vendor 1 Item C Vendor 2 Purchase Quote – Vendor 2 Item D Vendor 3 Purchase Quote – Vendor 3 Instead of forcing all four items into one quotation, the system groups the lines based on the selected vendors. The Result Purchase Quote 1 → Vendor 1 Purchase Quote 2 → Vendor 2 Purchase Quote 3 → … Continue reading How an Abu Dhabi-Based Diversified Holding Company Built a Budget-Controlled Procurement Process in Business Central →

Summary Business Central’s job queue silently powers a huge share of background processing — but when a job fails or simply stops running, teams often don’t find out until the downstream impact is already visible. Microsoft’s job queue notification feature closes that gap by pairing in-product alerts with external business events, so failures can trigger a Power Automate flow that notifies people over Outlook or Teams. Setup runs through the built-in Assisted Setup guide, with no custom code required to wire up the notification. We implemented this capability for a Home Loan Bank in the Maldives, where job queue reliability directly affects loan processing and regulatory reporting timelines. The result was a shift from reactive firefighting to proactive alerting — issues now reach the right team within minutes of a failure, not the next time someone happens to check the Job Queue Entries page. Table of Contents 01 Summary 02 Introduction 03 The Business Challenge 04 The Feature: External Notifications for Job Queue Failures 05 Setting It Up 06 Where Notifications Can Go 07 Business Impact 08 Best Practices 09 Case in Point: A Home Loan Bank in the Maldives 10 FAQs 11 Conclusion Introduction Most Business Central implementations lean on the job queue more heavily than anyone outside the finance or IT team realizes. Interest accruals, statement generation, data exports to regulators, scheduled reconciliations — all of it typically runs as unattended background jobs, quietly, on a schedule nobody actively watches. That’s exactly the problem. A background job is only reassuring while it’s running. The moment one fails — or worse, silently stops being scheduled at all — there’s no natural trigger that tells anyone. Business Central will log the failure on the Job Queue Entries page, but someone has to go looking for it. In a banking environment, where a missed job can mean a late regulatory submission or a loan status that doesn’t update overnight, that gap between “job fails” and “someone notices” is a real operational risk. Microsoft’s job queue notification capability, introduced in the Business Central 2024 release wave 2, addresses this directly — by letting failed job queue entries fire an external business event that can trigger a Power Automate flow, landing an alert in Outlook or Teams the moment something goes wrong. We recently implemented this for a Home Loan Bank in the Maldives, and this post walks through the feature and how it played out in that engagement. The Business Challenge Our client is a home loan bank operating in the Maldives, using Business Central to run a number of scheduled background processes — nightly interest calculations, loan repayment reminders, document generation, and reporting jobs that feed into compliance submissions. Before this implementation, the bank’s operations team relied on manually checking the Job Queue Entries page to confirm that scheduled jobs had run successfully. This created a few recurring problems: Job failures were often discovered hours later, typically when a downstream report or customer-facing document was missing or incorrect. There was no automatic escalation — a failed job stayed a failed job until someone happened to look. In a regulated lending environment, a delayed discovery could mean a delayed regulatory report, which carries its own compliance risk. The operations team wanted alerts to reach people directly in the tools they already used daily — Outlook and Teams — rather than adding another dashboard to check. The ask was simple to state and, until this feature existed, awkward to build: get an external notification the moment a scheduled job fails, without writing and maintaining custom integration code. The Feature: External Notifications for Job Queue Failures Business Central’s job queue has long supported in-product notifications when a background job fails. What’s new is the option to also raise this as an external business event — a signal that other systems, like Power Automate, can subscribe to and act on. In practical terms, this means a failed job queue entry can now do more than sit on a page waiting to be noticed. It can kick off a flow that sends an email through Outlook, posts a message in a Teams channel, or does both — all configured through Microsoft’s standard, no-code tooling rather than custom AL code or a middleware integration. The feature became generally available on November 1, 2024, and is enabled for admins, makers, and analysts to configure directly. Setting It Up 1 Step 1 Run the Assisted Setup Guide From the Assisted Setup page in Business Central, we launched the Set up Job Queue Notifications guide. This walks through the configuration step by step rather than requiring manual setup across multiple pages. 2 Step 2 Turn On Business Events On the second step of the guide, alongside the standard in-product notification option, we enabled Control notifications with business events (preview). This is the toggle that allows notifications to be managed externally, rather than only appearing inside Business Central itself. 3 Step 3 Connect the Power Automate Template On the final step, we followed the link to create an automated flow from the Job Queue Notification template. This opens the Job Queue Entries page, from which selecting Automate → Power Automate → Create automated flow brings up Microsoft’s ready-made Notify on Outlook or Teams when Job Queue in Business Central fails template. 4 Step 4 Configure Connections and Finish From the Create a flow page, we set up connections to Business Central, Outlook, and Teams. Selecting Edit in advanced mode let us adjust the flow to match the bank’s actual notification routing — which teams get which alerts, and through which channel — before finishing and applying the settings. Where Notifications Can Go The template supports routing failure alerts through either or both of these channels, depending on how a team prefers to work: OutlookSends an email the moment a monitored job queue entry fails, useful for teams that triage issues from their inbox. Microsoft TeamsPosts a message to a specified channel, useful for operations teams that monitor a shared channel … Continue reading From Silent Failures to Instant Alerts: Setting Up External Job Queue Notifications in Business Central →

This article demonstrates how to build a reusable Generic Data Deletion Utility in Microsoft Dynamics 365 Business Central that allows administrators and developers to safely delete individual records from any table using primary key values. Instead of creating separate utilities for different tables, this generic solution leverages RecordRef, FieldRef, and KeyRef to dynamically access Business Central tables at runtime. Summary Developed a generic data deletion utility for Microsoft Dynamics 365 Business Central. Enabled administrators to delete records from supported Business Central tables without creating table-specific code. Used RecordRef, FieldRef, and KeyRef to dynamically identify primary keys at runtime. Provided lookup functionality for selecting Business Central tables through the standard Object List. Added confirmation prompts before deletion to reduce accidental data loss. Designed the solution as a Processing Only report for administrative maintenance activities. Created a reusable framework that can be extended for future data maintenance utilities. Table of Contents 1. Introduction 2. The Business Problem 3. The Solution 3.1 Selecting the Business Central Table 3.2 Providing the Primary Key Values 3.3 Dynamically Identifying the Record 3.4 Confirming and Deleting the Record 3.5 Security and Permissions 4. Implementation 5. Business Impact 6. Frequently Asked Questions 7. Conclusion 1. Introduction Organizations in the pharmaceutical manufacturing industry frequently perform data cleanup activities during implementation, testing, data migration, and ongoing production support. Deleting specific records from Microsoft Dynamics 365 Business Central tables often requires custom-built utilities or direct database interventions, making the process time-consuming, less flexible, and difficult to maintain. To address this requirement, a Generic Data Deletion Utility was developed for a leading pharmaceutical manufacturing organization using Microsoft Dynamics 365 Business Central. By leveraging RecordRef, FieldRef, and KeyRef, the solution enables authorized users to dynamically locate and delete records from any Business Central table using primary key values without requiring table-specific deletion logic. This article explains the architecture of the solution, the AL programming concepts used, and how the framework provides a reusable and controlled approach for administrative data maintenance across standard and custom Business Central tables. 2. The Business Problem During implementation, testing, data migration, and production support activities, the organization frequently required the deletion of specific records from various Microsoft Dynamics 365 Business Central tables. Since each table has its own structure, fields, and primary key definitions, performing these deletions typically required custom-built utilities or temporary development efforts. This table-specific approach increased development effort, reduced operational efficiency, and made routine data maintenance activities more complex. The organization required a single reusable framework that could dynamically work with multiple Business Central tables without requiring separate deletion logic for each table. The Objective: Develop a generic data deletion utility that enables authorized users to safely identify and delete records from any Business Central table using primary key values while maintaining control and minimizing the risk of accidental data loss. 3. The Solution To simplify administrative data maintenance, a Generic Data Deletion Utility was developed in Microsoft Dynamics 365 Business Central. The solution provides a centralized utility that enables users to delete records from multiple tables without requiring separate deletion programs for each table. The tool allows authorized users to select a Business Central table, provide the required primary key values, locate the corresponding record dynamically, and delete it after user confirmation. The design supports both standard and custom Business Central tables while providing a flexible and reusable approach for controlled data management. The following sections describe the key components of the solution and explain how each feature contributes to making the tool dynamic, secure, and easy to maintain. 3.1 Selecting the Business Central Table The first step in the deletion process is selecting the Business Central table that contains the record to be removed. The request page provides fields for the Table Number and Table Name, allowing the user to identify the required standard or custom table. Instead of requiring users to manually remember table numbers, the Table No. field provides a drill-down option. This opens the standard All Objects with Caption page and filters the available objects to display only Business Central tables. TableObjects.SetRange( “Object Type”, TableObjects.”Object Type”::Table); if PAGE.RunModal( PAGE::”All Objects with Caption”, TableObjects) = Action::LookupOK then begin TableId := TableObjects.”Object ID”; TableCaption := TableObjects.”Object Caption”; end; Once a table is selected, the solution stores its object ID in the Table No. field and automatically displays the corresponding table name. This helps users verify that the correct table has been selected before providing the primary key values. The Table Name field is kept non-editable because its value is automatically retrieved from the selected Business Central table. Figure 1: Filtered Data Deletion request page for selecting the table and entering primary key values 3.2 Providing the Primary Key Values After selecting the required table, the user must provide the primary key values that uniquely identify the record to be deleted. Since each Business Central table has its own primary key structure, the solution supports primary key. The first key value is entered in the Primary Key field, while the Key 2 and Key 3 fields are available for tables that use multiple fields as part of their primary key. This enables the tool to locate records accurately regardless of the table structure. For example, a Customer record requires only the Customer No., whereas a Sales Line record requires multiple values such as the Document Type, Document No., and Line No. By supporting multiple key fields, the same utility can work across a wide range of standard and custom Business Central tables. Figure 2: Entering the primary key values required to uniquely identify a Business Central record. 3.3 Dynamically Identifying the Record Unlike conventional deletion utilities that are developed for a single table, this solution dynamically identifies records irrespective of the selected Business Central table. It uses the RecordRef, KeyRef, and FieldRef data types to work with table metadata at runtime, making the solution completely generic. After the user selects a table and enters the primary key values, the tool opens the selected table dynamically, retrieves its primary key definition, and applies … Continue reading Simplifying Record Management in Microsoft Dynamics 365 Business Central with a Generic Data Deletion Utility for Titan Labs →

Summary This blog explores how the Payables Agent in Microsoft Dynamics 365 Business Central (2025 Release Wave 1) transforms traditional Accounts Payable (AP) processes by leveraging AI to automate invoice processing for a Netherlands-based non-profit organization. Traditionally, finance teams spend considerable time manually entering invoice information, validating vendors, creating purchase invoices, and ensuring document accuracy. As invoice volumes grow, these repetitive tasks become increasingly time-consuming and susceptible to human error. The Payables Agent introduces an AI-assisted approach that automatically monitors a designated mailbox, extracts invoice information from PDF documents, identifies vendors, creates draft purchase invoices, and routes them for supervisor review before posting. This blog explains: The challenges associated with traditional Accounts Payable processing. How the Payables Agent works in Business Central. The configuration steps required to activate the agent. The end-to-end AI-powered invoice processing workflow. The business impact of automating Accounts Payable. Table of Contents Customer Scenario Business Challenges Solution Overview Solution Architecture Configuring the Payables Agent AI-Powered Invoice Processing Workflow Supervisor Review Process Business Impact Disclaimer FAQs Conclusion 1. Customer Scenario A finance department within a Netherlands-based non-profit organization processing hundreds of vendor invoices each month was experiencing increasing pressure to improve efficiency while maintaining financial accuracy and compliance. Invoice processing relied heavily on manual data entry. Finance users were responsible for opening incoming emails, downloading invoice PDFs, entering purchase invoice information into Business Central, validating vendors, and ensuring data accuracy before posting transactions. As invoice volumes continued to increase, the organization needed a smarter and more scalable solution capable of reducing repetitive work without compromising financial controls. The organization decided to leverage the new AI-powered Payables Agent introduced in Microsoft Dynamics 365 Business Central 2025 Release Wave 1. 2. Business Challenges The existing Accounts Payable process presented several operational challenges. 1. Manual Invoice Entry Finance users manually entered invoice information into Business Central, increasing processing time and effort. 2. Vendor Validation Each invoice required verification against existing vendor records before processing could continue. 3. Repetitive Administrative Work Processing hundreds of invoices each month resulted in significant administrative overhead and reduced productivity. 4. Human Errors Manual entry increased the likelihood of incorrect invoice values, vendor selection mistakes, and duplicate invoice processing. 5. Delayed Invoice Processing Large invoice volumes often delayed purchase invoice creation and subsequent payment processing. Business Need The organization required an intelligent solution capable of automating repetitive Accounts Payable activities while allowing finance teams to retain complete control over invoice validation and final approvals. 3. Solution Overview Microsoft introduced the Payables Agent as part of the AI capabilities available in Microsoft Dynamics 365 Business Central 2025 Release Wave 1. The agent is designed to streamline Accounts Payable operations by automating repetitive invoice processing tasks while maintaining financial controls. The Payables Agent continuously monitors a configured mailbox for incoming vendor invoice PDFs. Once a new invoice is detected, it automatically analyzes the document, extracts key information using AI, identifies the appropriate vendor, and prepares a draft purchase invoice for review. Once an invoice is received, the Payables Agent automatically performs the following tasks: Reads invoice information from the PDF document. Identifies the corresponding vendor. Extracts invoice header and line details. Creates a draft Purchase Invoice in Business Central. Notifies supervisors that a draft invoice is ready for review. Allows users to validate, finalize, and post the purchase invoice. Key Benefit: Rather than replacing finance professionals, the Payables Agent acts as an intelligent assistant that automates repetitive Accounts Payable activities while preserving financial governance, approval controls, and auditability. 4. Solution Architecture The Payables Agent follows a streamlined AI-assisted workflow that automates the processing of vendor invoices while ensuring finance teams retain full control over validation and posting. From receiving an invoice to creating a draft purchase invoice, each stage is designed to reduce manual effort and improve processing efficiency. Process Flow Vendor emails the invoice PDF to the designated mailbox. The invoice is received in the configured mailbox. The Payables Agent continuously monitors the mailbox for new invoices. AI Document Intelligence extracts the invoice information. The system matches the invoice with an existing vendor. A draft Purchase Invoice is automatically created. A supervisor reviews and validates the extracted information. The Purchase Invoice is finalized and posted into Business Central. Architecture Overview: The Payables Agent combines AI-powered document processing, automated vendor matching, and draft purchase invoice creation with human review to deliver a faster, more accurate, and well-governed Accounts Payable process. Core Components The following components work together to automate the invoice processing lifecycle while ensuring appropriate financial controls and governance. Component Purpose Vendor Email Sends vendor invoice PDFs to the designated mailbox. Configured Mailbox Receives incoming vendor invoices for processing. Payables Agent Monitors the mailbox and orchestrates the AI-driven invoice processing workflow. AI Document Intelligence Extracts invoice details such as vendor information, invoice number, dates, amounts, and line items. Vendor Matching Engine Matches extracted invoice data with existing vendor records in Business Central. Draft Purchase Invoice Automatically creates a draft purchase invoice using the extracted invoice information. Supervisor Review Allows finance users to validate the extracted information before posting. Purchase Posting Finalizes and posts the approved purchase invoice into Business Central. Key Takeaway: By combining AI-powered document intelligence with Business Central’s standard purchasing process, the Payables Agent minimizes manual data entry while ensuring every invoice is reviewed and validated before posting. 5. Configuring the Payables Agent Step 1 – Open the Payables Agent From the top-right corner of Microsoft Dynamics 365 Business Central, select the AP (Accounts Payable) icon to access the Payables Agent. Step 2 – Activate the Agent Enable the Payables Agent to begin AI-assisted invoice processing. Once activated, the agent becomes available to monitor incoming invoices and assist with the automatic creation of purchase invoices. Step 3 – Connect the Mailbox Configure the mailbox that will receive vendor invoice PDFs. The Payables Agent continuously monitors this mailbox and automatically imports incoming invoice documents as they arrive. After successful processing, the invoices are archived for future reference within Business Central. Step 4 – Vendor Matching … Continue reading Transforming Accounts Payable with AI: Configuring the Payables Agent in Microsoft Dynamics 365 Business Central for the Cradle to Cradle Products Innovation Institute (C2CPII) →

Summary Approval workflows in Microsoft Dynamics 365 Business Central provide a structured mechanism for multi-level document approvals. However, the standard approval email often lacks sufficient business context, making it difficult for approvers to take quick and informed decisions. In this implementation, for a Maldives-based loan and financial services organization, instead of modifying the core approval engine, we enhanced only the notification layer using Business Central’s event-driven architecture. The solution intercepts standard approval notifications and replaces them with a custom HTML email containing payment details and direct navigation links to the Payment Journal. This approach ensures the standard workflow remains fully intact while significantly improving the approval experience through richer and more actionable communication. Standard Business Central approval workflow remains unchanged. Custom HTML email notification introduced via an event-driven extension. Direct navigation to the Payment Journal enabled from the email. Faster and more informed approval decisions. Table of Contents Introduction Business Requirement Solution Overview Implementation Preview Video Business Impact Conclusion 1. Introduction Microsoft Dynamics 365 Business Central includes a powerful approval workflow engine that automates document approvals, supports multi-level approval chains, and automatically notifies approvers through email. Although the standard approval process works exceptionally well, the default email notification is intentionally simple. Approvers typically receive limited information and often need to open Business Central to locate the payment journal before they can review or approve the request. For organizations processing large volumes of financial transactions in a Maldives-based loan and financial services environment, this additional navigation slows down approvals and creates unnecessary effort. During one of our recent implementations in a Maldives-based lending and financial operations setup, the client wanted to improve the approval experience without changing Microsoft’s standard approval workflow. The objective was to retain every aspect of the existing workflow while enhancing only the email notification layer by introducing a modern, information-rich HTML email format. 2. Business Requirement The client wanted to achieve the following objectives: Preserve the standard Microsoft Dynamics 365 Business Central approval workflow. Keep all approval entries and workflow responses unchanged. Replace the standard approval email with a professional HTML email. Display important payment information directly inside the email body. Allow approvers to open the Payment Journal with a single click. Improve the overall approval experience without modifying Microsoft’s workflow engine. The primary goal was to enhance usability while maintaining full compatibility with the standard Business Central approval framework. 5. Preview Video The preview video section has been removed as per updated requirement. 6. Business Impact Implementing customized approval email notifications delivered several operational benefits while keeping Microsoft’s standard workflow engine fully intact. Improved User Experience Approvers receive all important payment information directly within the email, reducing the need to navigate through Business Central before reviewing requests. Faster Approval Decisions Direct navigation to the Payment Journal enables approvers to review and process approvals much more quickly. Better Visibility Payment amount, vendor information, posting date, and approval sequence are immediately visible, making approvals easier and reducing the chance of overlooking important details. Easier Document Verification Supporting invoice attachments can be reviewed directly from the Payment Journal before approving payments. Upgrade-Friendly Solution Because the implementation relies entirely on standard Microsoft Dynamics 365 Business Central events, no modifications are made to the core approval engine, ensuring future upgrades remain smooth and low-risk. 7. Conclusion Microsoft Dynamics 365 Business Central’s event-driven extensibility model allows developers to significantly enhance the user experience without modifying standard application logic. By leveraging the OnBeforeCreateApprovalEntryNotification event, we replaced the default approval email with a professional HTML notification while preserving the complete standard approval workflow. Approvers now receive richer payment information, can navigate directly to the Payment Journal, and have quick access to supporting documents—all without altering Microsoft’s workflow engine. This implementation demonstrates how targeted customizations can greatly improve productivity and usability while remaining fully aligned with Microsoft’s recommended extension development practices. Ready to modernize your Business Central approval experience? Standard approval emails often lack context, forcing approvers to open Business Central repeatedly just to review basic payment details. With event-driven customization, you can transform these notifications into rich, structured HTML emails that improve decision-making speed and user experience. CloudFronts helps organizations extend Microsoft Dynamics 365 Business Central with smart, upgrade-safe customizations, workflow enhancements, and finance automation solutions. For more information, reach out at transform@cloudfronts.com.

Summary This blog highlights how Microsoft Dynamics 365 Business Central can be used to implement Amount-Specific and Multi-Approver Workflows to automate approval management across business operations. In many organizations, approval processes are handled manually through emails, spreadsheets, and verbal confirmations. These manual approval systems often create delays, missing approvals, operational bottlenecks, and poor audit visibility. The implementation of approval workflows in Business Central helps organizations automate approval routing based on transaction amount, approval hierarchy, department, and business rules. Using Business Central Workflow and Approval Management functionality, organizations can: This blog explains: 1] The operational challenges caused by manual approval processes 2] How Amount-Specific workflows can be implemented in Business Central 3] How Multi-Approver workflows improve approval governance 4] The workflow architecture and approval routing logic 5] The business impact achieved through workflow automation Table of Contents Business Scenario A growing manufacturing and distribution organization was facing significant challenges in managing approvals across procurement, finance, and operations. The organization handled: However, the approval process was largely manual. Employees submitted requests through emails and internal communication channels, after which managers manually reviewed and approved transactions. For higher-value transactions, approvals often required escalation to senior management or finance leadership. This manual process created several operational issues: 1] Delays in approvals due to manual follow-ups 2] Lack of visibility into approval status 3] Missing audit tracking for approved and rejected transactions 4] Difficulty enforcing amount-based approval policies 5] Increased risk of unauthorized approvals 6] Approval bottlenecks during manager unavailability The organization required a scalable approval system that could automate approval routing while ensuring strict financial control and governance. Solution Overview To streamline approval management, Amount-Specific and Multi-Approver workflows were implemented using Microsoft Dynamics 365 Business Central. The objective was simple: Automatically route approvals to the correct approvers based on transaction amount and business hierarchy. With this implementation: The workflow solution was implemented using: Amount-Specific Approval Workflow Understanding Amount-Based Approval Routing The organization required different approvers depending on the transaction amount. Example approval structure: Amount Range Approver Up to 50,000 Team Lead 50,001 – 2,00,000 Department Manager Above 2,00,000 Finance Director Using Business Central workflows, approval conditions were configured based on document amount. This ensured: Example: Purchase Approval Workflow When a Purchase Order is created: Scenario 1 — Low Amount Approval If Purchase Amount <= 50,000: 1] Send approval request to Team Lead 2] Team Lead approves 3] Document is automatically released Scenario 2 — Medium Amount Approval If Purchase Amount > 50,000 and <= 2,00,000: 1] Send approval request to Department Manager 2] Manager approves 3] Document is automatically released Scenario 3 — High Amount Approval If Purchase Amount > 2,00,000: 1] Send approval request to Procurement Head 2] Send approval request to Finance Director 3] Both approvals are completed 4] Document is released This automated routing eliminated manual intervention completely. Multi-Approver Workflow Structure Understanding Multi-Approver Workflows Certain business processes required approvals from multiple departments before transactions could proceed. Business Central workflows were designed to support: Sequential Approval Example Approval moves step-by-step between users. Example: Employee → Team Lead → Manager → Finance Head Each approver receives the approval request only after the previous approver completes approval. This ensures strict control and structured review processes. Department-Based Multi Approval Some transactions required validations from multiple departments. Example: Only after all approvals are completed does the workflow continue further. Workflow Architecture Approval Workflow Process Flow The workflow engine automatically evaluates the conditions and routes approvals accordingly. Approval User Setup Configuring Approval Hierarchy The approval hierarchy was managed using the Approval User Setup page in Business Central. Important configurations included: Field Purpose User ID Business Central User Approver ID Direct Approver Purchase Amount Approval Limit Purchase approval limit Unlimited Approval Unlimited approval rights Substitute Backup approver Request Amount Approval Limit Generic approval limit This setup formed the foundation for workflow automation. Handling Complex Approval Scenarios One important aspect of the implementation was handling complex approval scenarios automatically. The system managed: These validations and routing decisions happened automatically in the background. Users only needed to submit the transaction — the system handled the approval logic. Business Impact 1] Faster Approval Processing Low-value transactions were approved quickly without unnecessary managerial involvement. Approval cycle time reduced significantly. 2] Improved Financial Control High-value transactions automatically required senior management approval. This reduced the risk of unauthorized approvals. 3] Increased Operational Efficiency Employees no longer needed to manually follow up for approvals through emails or calls. The system automatically notified approvers and tracked pending approvals. 4] Better Audit Tracking All approval actions were stored inside Business Central. Organizations could track: 5] Scalable Approval Management The organization could now handle increasing transaction volume without increasing operational overhead. The workflow engine scaled efficiently with business growth. To conclude, approval management is a critical component of any ERP implementation, especially for organizations dealing with procurement, finance, and operational governance. By implementing Amount-Specific and Multi-Approver Workflows in Microsoft Dynamics 365 Business Central, organizations can automate approval routing while maintaining strong financial and operational control. What was previously handled manually through emails and spreadsheets can now be managed automatically through a structured workflow engine inside Business Central. This transformation not only improves operational efficiency but also strengthens compliance, transparency, and audit readiness across the organization. If your Business Central environment requires custom approval workflows, amount-based approval automation, or multi-department approval management, implementing a well-designed workflow architecture can significantly improve business operations and user productivity. Ready to modernise your Workflows your D365 Business Central?CloudFronts builds scalable Power Platform and Dynamics 365 solutions that replace legacy Processes & Automations infrastructure. Reach out at transform@cloudfronts.com.

Summary Microsoft Dynamics 365 Business Central keeps your business future‑ready with regular updates that improve speed, security, and usability. For customers, this means smoother workflows, fewer disruptions, and access to the latest features without extra effort. Updates are scheduled with flexibility, tested in sandboxes, and designed to fit around your operations so you stay focused on running your business while Business Central takes care of the rest. Steps to Achieve Goal Access the Admin Center Review Available Updates Schedule the Update Coordinate with Production Scheduling Test in Sandbox To conclude, updating Microsoft Dynamics 365 Business Central isn’t just a technical task it’s a way to keep your business secure, efficient, and ready for growth. Every update is designed with customers in mind: fewer disruptions, stronger protection, and smarter features that make daily work easier. By preparing ahead and using sandbox testing, you can ensure updates fit seamlessly into your operations. With Business Central, staying current means staying confident your system evolves so your business can keep moving forward without missing a step. Connect with CloudFronts to get started at transform@cloudfonts.com

Summary This blog explains how to effectively track and debug job queue failures in Microsoft Dynamics 365 Business Central. In many Business Central implementations, job queues are used to automate critical background processes such as posting transactions, sending emails, synchronizing data, and running reports. However, when these jobs fail, identifying the root cause can become challenging due to limited visibility and lack of proper debugging practices. This blog provides a structured approach to monitor job queue failures, analyze error logs, and debug issues efficiently using built-in tools and development techniques. This blog explains: 1] Common reasons behind job queue failures 2] How to track failed job queue entries 3] How to debug job queue errors using AL 4] Best practices for logging and monitoring 5] Business impact of efficient job queue handling Table of Contents Customer Scenario A growing organization using Microsoft Dynamics 365 Business Central had automated multiple backend processes using Job Queues. These included: 1] Automatic posting of invoices 2] Scheduled report generation 3] Email notifications to customers 4] Data synchronization with external systems While automation improved efficiency, the team started facing frequent job queue failures. The challenges included: 1] No clear visibility of why jobs were failing 2] Errors appearing without sufficient details 3] Delays in critical processes like posting and integrations 4] Manual intervention required to restart failed jobs 5] Increased dependency on technical teams Since job queues run in the background, users were often unaware of failures until business operations were impacted. The organization needed a structured way to track, analyze, and debug job queue failures efficiently. Solution Overview To address these challenges, a systematic approach was implemented to monitor and debug job queue failures within Business Central. The goal was simple: Enable quick identification and resolution of job queue failures with minimal effort. With this approach: The workflow now looks like this: Functional Implementation Approach The implementation focuses on improving visibility, debugging capability, and system reliability. Monitoring Job Queue Entries Business Central provides a dedicated Job Queue Entries page where all scheduled jobs are listed. Key fields to monitor: 1] Status (Ready, In Process, Error) 2] Earliest Start Date/Time 3] Recurrence settings 4] Object Type and Object ID 5] Last Error Message When a job fails, the status changes to Error, which becomes the primary trigger for investigation. Analyzing Job Queue Log Entries Each job queue execution creates log entries that store execution details. These logs provide: 1] Error messages 2] Execution time 3] Call stack (in some cases) 4] Number of attempts This is the first place to check when debugging a failure. Using “Show Error” Functionality The “Show Error” action provides detailed error messages generated during execution. This helps identify: 1] Missing data 2] Invalid field values 3] Permission issues 4] Posting errors Debugging Job Queue Failures Debugging job queues requires a slightly different approach compared to normal execution. Attaching Debugger to Session Since job queues execute in the background, debugging requires attaching to the active session where the job is running. Steps: 1] Go to Help and Support page 2] Click on Attach Debugger to this Session 3] Set breakpoints in the relevant codeunit 4] Trigger or wait for the job queue to execute This method allows you to debug the exact session where the job queue is running, making it easier to trace issues in real time. Using Breakpoints in Codeunits Most job queues run codeunits. Developers should: 1] Identify the Codeunit ID from Job Queue Entry 2] Add breakpoints in key logic areas 3] Re-run the job queue 4] Step through execution Common Causes of Failures Some frequent reasons include: 1] Missing mandatory fields 2] Incorrect filters in code 3] Permission issues for background user 4] Deadlocks or record locking 5] Integration/API failures Handling Complex Scenarios In real-world implementations, job queue failures can involve complex scenarios. Logging Custom Errors Developers can enhance debugging by adding custom logs in AL code. For example: 1] Logging key variable values 2] Capturing intermediate processing steps 3] Writing meaningful error messages This makes troubleshooting faster and more accurate. Retry Mechanism Job queues support automatic retries. Proper configuration ensures: 1] Temporary issues are resolved automatically 2] Manual intervention is minimized 3] System resilience improves Handling Integration Failures When job queues interact with external systems: 1] API timeouts must be handled 2] Response validation should be implemented 3] Retry logic should be added Business Impact 1] Reduced Downtime Quick identification of job queue failures ensures minimal disruption to business operations. 2] Improved System Reliability With proper monitoring and debugging, automated processes become more stable. 3] Increased Developer Productivity Developers spend less time identifying issues and more time resolving them. 4] Faster Issue Resolution Clear logs and debugging techniques reduce troubleshooting time significantly. 5] Scalable Automation Organizations can confidently automate more processes without fear of silent failures. Preview Video The preview video demonstrates how to track and debug job queue failures in Business Central. Video highlights: Opening Job Queue Entries page Identifying failed jobs Viewing Job Queue Log Entries Using “Show Error” functionality Attaching debugger from Visual Studio Code Demo: Debugging a Job Queue Failure in Business Central Final Thoughts Job queues are a powerful feature in Microsoft Dynamics 365 Business Central that enable automation of critical business processes. However, without proper monitoring and debugging practices, failures can go unnoticed and impact operations. By implementing structured tracking, logging, and debugging techniques, organizations can transform job queue management from a reactive process into a proactive one. What was once a difficult and time-consuming troubleshooting activity can now be handled efficiently with the right approach—ensuring smooth and reliable system performance. If your Business Central environment is facing recurring job queue failures or requires optimization of background processes, consider implementing structured debugging and monitoring practices to improve overall system efficiency. Connect with CloudFront’s to get started at transform@cloudfonts.com.