In today’s rapidly evolving AI landscape, organizations are seeking scalable, secure, and efficient ways to deploy intelligent agents. Agent Bricks offers a modular, low-code approach to building AI agents that are reusable, compliant, and production-ready. This blog post explores the evolution of AI leading to Agentic AI, the prerequisites for deploying Agent Bricks, a real-world HR use case, and a glimpse into the future with the ‘Ask Me Anything’ enterprise AI assistant.  Prerequisites to Deploy Agent Bricks  Use Case: HR Knowledge Assistant  HR departments often manage numerous SOPs scattered across documents and portals. Employees struggle to find accurate answers, leading to inefficiencies and inconsistent responses. Agent Bricks enables the deployment of a Knowledge Assistant that reads HR SOPs and answers employee queries like ‘How many casual leaves do I get?’ or ‘Can I carry forward sick leave?’.  Business Impact:  Agent Bricks in Action: Deployment Steps  Figure 1: Add data to the volumes  Figure 2: Select Agent bricks module     Figure 3: Click on Create Agent option to deploy your agent     Figure 4: Click on Update Agent option to update deploy your agent  Agent Bricks in Action: Demo   Figure 1: Response on Question based on data present in the dataset     Figure 2: Response on Question asked based out of the present in the dataset  To conclude, Agent Bricks empowers organizations to build intelligent, modular AI agents that are secure, scalable, and impactful. Whether you’re starting with a small HR assistant or scaling to enterprise-wide AI agents, the time to act is now. AI is no longer just a tool it’s your next teammate. Start building your AI workforce today with Agent Bricks.  We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudFronts.com Start Your AI Journey Today !!

Managing inventory effectively is essential for any organization aiming to balance stock levels, minimize excess inventory costs, and ensure timely order fulfillment.Microsoft Dynamics 365 Business Central provides a range of tools that simplify and automate inventory control – helping businesses maintain the right stock at the right time. In this post, we’ll walk through the key features and planning tools available in Business Central’s Inventory Management module. Pre-requisite: 1. Access the Item List Page Start by opening the Item List page. This page offers a complete overview of all active items, including quantities on hand, reorder points, and categories. It serves as the foundation for any inventory planning activity. 2. Open an Item Card Select an item from the list to view its Item Card, where you configure how the system manages, replenishes, and forecasts that product. The setup on this page directly affects how purchase or production orders are generated. a. Configure Replenishment Method and Reordering Policy Under the Replenishment tab, you can define how stock for each item should be refilled when levels drop below a specific threshold. Replenishment Methods include: Lead Time:Set the expected number of days it takes to receive, produce, or assemble an item. This ensures the system plans replenishment activities in advance. Reordering Policies: b. Using Stock Keeping Units (SKUs) for Location-Specific Planning SKUs allow tracking of an item by individual location or variant, enabling businesses to manage stock independently across warehouses or stores.This approach ensures accurate availability data, reduces fulfillment errors, and supports better demand analysis for each location. c. Demand Forecasting The Demand Forecast feature in Business Central helps predict future requirements by analyzing past sales and usage patterns.Forecasts can be system-generated or manually adjusted to reflect upcoming promotions, seasonal variations, or expected demand spikes. d. Requisition (MRP/MPS) Planning The Requisition Worksheet supports Material Requirements Planning (MRP) and Master Production Scheduling (MPS). It automatically reviews forecasts, current stock, and open orders to suggest what needs to be purchased or produced. The system lists recommendations such as item names, quantities, and suppliers.Once reviewed, click Carry Out Action Messages to create purchase or production orders directly — saving time and minimizing manual work. e. Aligning with Sales Orders When a Sales Order is entered, Business Central dynamically recalculates availability.If demand exceeds what was forecasted, the system proposes additional purchase or production orders to prevent shortages and maintain customer satisfaction. To conclude, Dynamics 365 Business Central simplifies inventory control by automating procurement, forecasting demand, and synchronizing stock levels with actual sales.By using replenishment rules, SKUs, and requisition planning, businesses can improve inventory accuracy, reduce costs, and deliver orders faster – all within a single integrated ERP system. We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudFronts.com

Many growing companies work with multiple legal entities. Each month, they exchange bills, services, or goods between companies. Doing this manually often leads to delays and mistakes. Microsoft Dynamics 365 Business Central helps fix that through Intercompany Automation. This feature lets you post one entry in a company, and the system automatically creates the same transaction in the other company. Let’s see how you can set it up and how it works with a real example. Why Intercompany Automation Matters If two companies within the same group trade with each other, both sides must record the same transaction, one as a sale and one as a purchase. When done manually, the process is slow and can cause mismatched balances. Automating it in Business Central saves time, reduces errors, and keeps both companies’ financials in sync automatically. Step 1: Setup Process 1. Turn on Intercompany Feature Open Business Central and go to the Intercompany Setup page. Turn on the setting that allows the company to act as an Intercompany Partner. 2. Add Intercompany Partners Add all related companies as partners. For example, if you have Company A and Company B, set up each as a partner inside the other. 3. Map the Chart of Accounts Make sure both companies use accounts that match in purpose. Example: 4. Create Intercompany Customer and Vendor 5. Create Intercompany Journal Templates Use IC General Journals to record shared expenses or income regularly. You can automate them using job queues or recurring batches. Step 2: Automation in Action Once the setup is complete, every time a user posts a sales invoice or general journal related to an Intercompany Customer or Vendor, Business Central creates a matching entry in the partner company. Both companies can see these transactions in their IC Inbox and Outbox. You can even add automation rules to post them automatically without approval if desired. Step 3: Use Case – Monthly IT Service Charges Scenario: The Head Office provides IT services to a Subsidiary every month for ₹1,00,000. Steps: Both companies now have matching entries, one as income and one as expense, without any manual adjustments. Result: Transactions are accurate, time is saved, and your accountants can focus on analysis rather than repetitive posting. To conclude, automating intercompany postings in Business Central makes financial management simple and reliable. Once configured, it ensures transparency, reduces errors, and speeds up reporting. I Hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com.

Sometimes, it becomes necessary to correct a posted transaction. Instead of manually adjusting or attempting to delete it, you can utilize the reverse functionality. Reverse journal postings are helpful for correcting mistakes or removing outdated accrual entries before creating new ones. A reversal mirrors the original entry but uses the opposite sign in the Amount field. It must use the same document number and posting date as the original. After reversing, the correct entry must be posted. Only entries created from general journal lines can be reversed, and each entry can be reversed only once. To undo a receipt or shipment that hasn’t been invoiced, use the Undo action on the posted document. This applies to Item and Resource quantities. You can undo postings if an incorrect negative quantity was entered (for example, a purchase receipt with the wrong item quantity and not yet invoiced). Similarly, incorrect positive quantities posted as shipped but not invoiced, such as sales shipments or purchase return shipments. can also be undone. Pre-requisites Business Central onCloud Steps: Open the transaction you wish to reverse. In this case, we aim to reverse the payment for the customer shown below. Click on Ledger Entries to view all transactions associated with this customer. As shown, this payment has already been applied to an invoice. Therefore, you must first unapply the payment before proceeding. Use the Unapply Entries action button to unapply the entries for the selected customer. Once you successfully unapplied payment you can see “remaiing amount” is equal to “Amount” field. Now click on “Reverse Transaction”. You can view the related entries for this transaction. Click the Reverse button, and a pop-up will appear once the reversal entries have been posted for the selected transaction. The reverse entry has now been created, reflecting the same document number and amount. Leveraging the reverse transaction functionality in Business Central enables businesses to correct errors seamlessly, improve operational efficiency, and uphold the integrity of their financial data. Whether managing invoices, payments, or other ledger entries, this feature is an essential tool for maintaining transparency and accuracy in your financial workflows. To Conclude, the reverse transaction feature in Business Central is a powerful tool that simplifies the process of correcting posted transactions. Instead of manually adjusting or deleting entries, you can efficiently reverse them, ensuring your financial records remain accurate and consistent. We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

When working on report customizations in Microsoft Dynamics 365 Business Central, one common challenge is maintaining a consistent layout regardless of how many lines are present in the data source. This situation often arises in reports like Purchase Orders, Sales Orders, or Invoices, where the line section expands or contracts based on the number of lines in the dataset. However, certain business scenarios demand a fixed or uniform presentation, such as when a client wants consistent spacing or placeholders for manual inputs. This article demonstrates how you can achieve this flexibility purely through RDLC layout design – without making any changes in AL or dataset logic. Business Requirement The objective was to design a Purchase Order report where the line area maintains a consistent structure, independent of how many lines exist in the actual data. In other words, the report layout should not necessarily reflect the dataset exactly as it is. The idea was to ensure visual uniformity while keeping the underlying data logic simple. Proposed Solution The solution was implemented directly in the RDLC report layout by creating two tables and controlling their visibility through expressions. There was no need to align them in the same position one table was placed above the other. RDLC automatically handled which one to display at runtime based on the visibility conditions. Table 1 – Actual Purchase Lines Displays the real data from the Purchase Line dataset. Table 2 – Structured or Blank Layout Displays a predefined structure (for example, blank rows) when fewer lines are available. This design ensures that whichever table meets the visibility condition is rendered, maintaining layout flow automatically. Implementation Steps 1. Add Two Tables in the RDLC Layout 2. Set Visibility Conditions To control which table appears at runtime, open each table’s properties and go to:Table Properties → Visibility → Hidden → Expression Then apply the following expressions: For Table 1 (Actual Purchase Lines) =IIF(CountRows(“DataSet_Result”) <= 8, True, False) Hides the actual data table when the dataset has fewer rows. For Table 2 (Structured or Blank Layout) =IIF(CountRows(“DataSet_Result”) > 8, True, False) Hides the structured or blank table when enough data rows are available. Note: The number “8” is just an example threshold. You can set any value that fits your design requirement. Result At runtime: The RDLC engine handles layout adjustment, ensuring the report always looks uniform and visually balanced – without any need for AL code changes or temporary data handling. Advantages of This Approach Benefit Description No AL Code Changes Achieved entirely within RDLC layout. Upgrade Friendly Dataset and report objects remain unchanged. Automatic Layout Flow RDLC adjusts which table is displayed automatically. Professional Appearance Ensures consistent formatting and structure across all reports. Key Takeaways This simple yet effective approach shows that report design in Business Central can be made flexible without altering data logic.By using two tables with visibility expressions, you can create reports that adapt their appearance automatically – keeping the layout professional, stable, and easy to maintain. We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

For any Indian business running on Microsoft Dynamics 365 Business Central, tax compliance isn’t optional, it’s foundational. The Goods and Services Tax (GST) framework is complex and manually managing it is a high-risk gamble. This guide isn’t just a list of steps; it’s your definitive blueprint for configuring Business Central’s powerful Indian localization features to handle GST seamlessly. We will transform your ERP from a standard ledger into a fully automated, compliance-ready machine. Ready to banish tax-related data entry errors and audit anxiety? Let’s dive in and set up the system correctly, from defining your GSTINs to mastering the G/L posting matrix. Microsoft Dynamics 365 Business Central offers robust localization features for India, including comprehensive support for the Goods and Services Tax (GST). Properly configuring GST is essential for calculating, recording, and settling taxes on all your inward and outward supplies, ensuring compliance with Indian tax laws. This guide provides a straightforward, step-by-step process for setting up GST in Business Central, based on Microsoft’s best practices. Phase 1: Laying the Foundation (Tax Periods & Registration) The initial phase involves setting up the legal and temporal frameworks for your GST configuration. Step 1: Define Tax Accounting Periods (GST Calendar) The GST regime operates on a specific timeline, and you need to define this within Business Central. Step 2: Establish Your GST Registration Numbers (GSTINs) Your Goods and Service Tax Payer Identification Number (GSTIN) is critical for identifying your tax entity and the state you operate in. Phase 2: Core Configuration (G/L Accounts and Masters) This phase links the statutory requirements with your company’s general ledger structure. Step 3: Configure GST Groups and HSN/SAC Codes These setups classify your goods and services for accurate rate calculation. Step 4: Define the GST Posting Setup (The Accounting Link) This is perhaps the most crucial step, as it determines which General Ledger (G/L) accounts are used to post GST amounts. Step 5: Set Up GST Rates With your Groups and HSN/SAC codes defined, you now specify the actual tax percentages. Phase 3: Master Data Integration (Connecting the Dots) The final phase ensures that your business entities and locations are linked to the defined GST rules. Step 6: Update Company and Location Information Your company’s primary details must be GST-compliant. Step 7: Configure Customer and Vendor Master Data For every trading partner, you must define their GST status and registration details. To conclude, by following these seven steps, your Indian company’s Business Central environment will be fully configured to handle GST calculations automatically. This setup allows the system to determine the correct tax component (CGST, SGST, or IGST), apply the right rate, and post the amounts to the designated G/L accounts, simplifying your day-to-day transactions and preparing you for GST settlements and reporting. I Hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com.

Integrating Dynamics 365 (D365) with external systems using Azure Logic Apps is one of the most common patterns for automation. But in real-world projects, things rarely go smoothly – API throttling, network timeouts, and unexpected data issues are everyday challenges. Without proper error handling and retry strategies, these issues can result in data mismatches, missed transactions, or broken integrations. In this blog, we’ll explore how to handle errors and implement retries in D365 Logic App integrations, ensuring your workflows are reliable, resilient, and production-ready. Core Content 1. Why Error Handling Matters in D365 Integrations Without handling these, your Logic App either fails silently or stops execution entirely, causing broken processes.  2. Built-in Retry Policies in Logic Apps What They Are:Every Logic App action comes with a retry policy that can be configured to automatically retry failed requests. Best Practice: 3. Handling Errors with Scopes and “Run After” Scopes in Logic Apps let you group actions and then define what happens if they succeed or fail. Steps: Example: 4. Designing Retry + Error Flow Together Recommended Pattern: This ensures no transaction is silently lost. 5. Handling Dead-lettering with Service Bus (Advanced) For high-volume integrations, you may need a dead-letter queue (DLQ) approach: This pattern prevents data loss while keeping integrations lightweight. 6. Monitoring & Observability Error handling isn’t complete without monitoring. Building resilient integrations between D365 and Logic Apps isn’t just about connecting APIs—it’s about ensuring reliability even when things go wrong. By configuring retry policies, using scopes for error handling, and adopting dead-lettering for advanced cases, you’ll drastically reduce downtime and data mismatches. Next time you design a D365 Logic App, don’t just think about the happy path. Build error handling and retry strategies from the start, and you’ll thank yourself later when your integration survives the unexpected. We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

When developing in Microsoft Dynamics 365 Business Central, you spend a lot of time working in Visual Studio Code. To streamline productivity and keep projects well-organized, workspaces in Business Central AL play a critical role. In this blog, we’ll explore what workspaces are, why they matter, and how you can use them effectively in your AL development journey. What is a Workspace in Business Central AL? A workspace in Visual Studio Code is essentially a container that holds your project’s structure, settings, and configurations. In Business Central AL development, a workspace defines: In short, a workspace ensures that everything needed to build and deploy an extension is neatly bundled together. Benefits of Using Workspaces Creating and Managing Workspaces Tip: Save your workspace using File > Save Workspace As… so you can reopen it quickly in future. Example: Multi-root Workspace When working with multiple extensions in a workspace, handling dependencies used to mean installing each required app one by one. Now, the development environment can automatically look at the dependency graph in your workspace and publish the necessary projects along with the one you selected. This way, you can focus on building and testing without worrying about missing dependencies. Imagine you’re working with multiple extensions in your Business Central environment: From the diagram: Base App ALProject1 ALProject2 ALProject3 Adding Folder to Workspace. Saving Workspace. Creating a separate folder to store workspaces. Publishing Full Dependency. This allows you to debug, build, and manage all the extensions from a single VS Code instance. Best Practices for Workspaces To conclude, workspaces in Business Central AL are more than just folders — they are the foundation of your development environment. By structuring your projects with well-maintained workspaces, you ensure smoother collaboration, better organization, and efficient extension deployment. If you’re just starting with AL, experiment with single-project workspaces, and as you grow, explore multi-root setups to manage larger development scenarios. We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

One limitation while working with MS forms is the 1 GB limit on file submission through the forms. Many of you guys are must be using Forms to get files from users or clients outside your organizations and those files can be over 1GB.  In this blog I will show you how you let users submit files over 1 GB through MS Forms and store this response into a SharePoint list. So let’s being..  Approach:   MS Form stores all the files onto your one drive, One drive also offers a feature called “Request Files” using which you can create a shareable link to a one drive folder in which anyone with the link can upload files and it has no limit over the size of the file.   So instead of using the forms upload file feature we will be using shareable link from the Request File feature on the form using which users will be able to submit documents of any size. Let’s see how to do this.  Create Shareable link to a one drive folder using Request File Feature.  Copy this link and save it we will be using this link in our MS form.  Create MS Form.  You can add the link as you want on the form you can also add it in your sections sub title (Both these are just examples or ideas of how you can show users this link.)  Stored attachments in one drive.  We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com.

Power BI is one of the most popular tools for business intelligence and reporting. But out-of-the-box reports often fall short when it comes to addressing real-world business needs. To truly maximize its potential, Power BI can be customized with advanced features like conditional formatting, multi-page designs, and Row-Level Security (RLS). In this blog, we’ll walk through a practical example of customizing a Power BI report for territory-based account analysis. Even if you’re a beginner, this guide will help you understand the steps and how you can apply them in your own reports. Problem Statement The business needed to analyze accounts by sales territory. The default Power BI report had limitations: – All territories looked the same on the map, making it difficult to differentiate them. – Managers had no easy way to drill into account-level details. – Sensitive account data was visible to everyone, creating compliance risks. Clearly, a more structured and secure approach was needed. Solution Approach Using DAX, we created a measure to assign each territory a unique color. This helped managers quickly distinguish regions on the map. 2. Multi-Page Report Design We structured the report across three pages: – Page 2 – Drill-Through Account Details: Clicking on a territory brings you here to view specific accounts. – Page 3 – Tabular Data View: A table version of Page 2 for exporting and validating data. 3. Row-Level Security (RLS) RLS was applied so each Territory Manager only sees data for their assigned region. This not only secures data but also builds trust among users. Key Learnings – Beginners can start small: apply conditional formatting to bring clarity to visuals. – Multi-page design makes reports more user-friendly than cluttering everything on one screen. – RLS is essential for real-world deployments, ensuring only the right people see the right data. To conclude, by customizing Power BI with conditional formatting, multi-page design, and Row-Level Security, even a beginner can create professional-grade reports. These enhancements transform Power BI into a secure, role-based tool that aligns with how businesses actually operate. We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com.