Inventory is the core of many businesses. Whether you’re selling products, making goods, or managing a supply chain, keeping the right stock at the right time is key. Microsoft Dynamics 365 Business Central helps businesses handle inventory with ease and clarity. 1. Central Item List Item lists are the backbone of inventory management. Business Central lets you create a structured list of all your products—whether you buy them, sell them, or just store them. This organized list becomes the single source of truth across all departments. 2. Real-Time Inventory Levels Business Central keeps track of: This helps businesses plan better and fulfill orders faster without confusion. 3. Multi-Location Tracking If you manage inventory in multiple places (like stores, warehouses, or branches), Business Central supports that too. You can: 4. Reorder and Stock Planning With built-in reorder logic, Business Central tells you when to buy and how much to buy. It considers: This reduces guesswork and supports a smooth procurement process. 5. Purchase and Sales Integration When a purchase order is received or a sales order is shipped, inventory updates automatically. This minimizes the need for manual updates and keeps everyone on the same page. 6. Lot and Serial Number Tracking Business Central supports lot numbers and serial numbers. This helps with: 7. Inventory Valuation Methods You can choose how to value your inventory: This supports accurate financial reporting and cost control. 8. Inventory Transfers Do you need to move items from one location to another? Use transfer orders. You can record: 9. Inventory Adjustments Sometimes physical counts don’t match system data. Business Central allows easy stock corrections for: 10. Reports and Insights With built-in reports and dashboards, you can track: These insights will assist you in making well-informed decisions and planning ahead. Why It Matters Good inventory management helps you: Business Central gives you the tools to manage stock simply and efficiently. If you’re using spreadsheets or disconnected tools to manage inventory, now is a good time to explore Business Central. It gives you more control, better insights, and smoother operations—all in one place. We hope you found this blog useful. If you would like to discuss anything, you can reach out to us at transform@cloudfronts.com.

A well-structured Chart of Accounts (COA) is essential for achieving accuracy and efficiency in financial management. In Microsoft Dynamics 365 Business Central, the COA plays a key role in organizing financial data, supporting compliance, and enabling insightful reporting. By implementing effective strategies and tips, businesses can create a reliable and scalable financial environment. Below, we explore practical steps for setting up a successful environment with the Chart of Accounts in Business Central. Understand the Basics of the Chart of Accounts The Chart of Accounts in Business Central provides a framework for categorizing financial transactions. Key components include: Organize accounts into primary groups such as Assets, Liabilities, Equity, Income, and Expenses. Define Clear Financial Goals Establishing clear financial goals helps align the COA structure with business objectives: Streamline Account Structures To maintain efficiency, simplify the Chart of Accounts structure: Develop a Logical Numbering System A structured numbering system improves navigation and consistency: Configure Posting Groups Posting groups automate how transactions are allocated to accounts: Perform Testing and Validation Ensure the setup supports business requirements by testing thoroughly: Plan for Future Needs Business needs evolve over time, requiring flexibility in financial systems: To encapsulate, creating a successful financial environment with Microsoft Dynamics 365 Business Central’s Chart of Accounts involves careful planning, structured setup, and ongoing maintenance. By simplifying account structures, leveraging dimensions, and ensuring scalability, businesses can build a COA that supports both current operations and future growth. These strategies and tips will help your organization manage finances more effectively and ensure your systems are aligned with broader business goals. If you’d like guidance on setting up dimensions, configuring posting groups, or optimizing reporting, feel free to ask! We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfonts.com.

References Configure Session Timeout – Dynamics NAV | Microsoft Learn Pre-requisites Microsoft Dynamics NAV 2016. Introduction In this blog, I am going to showcase how to set session timeout on the NAV window. Scenario: The session timeout is 15 minutes; if the client connection is inactive for more than 15 minutes, the connection is lost. Let’s have a look at the setting for session time out. Hope this helps!

Introduction In this blog, I will demonstrate using Standard Journal functionality in Dynamics 365 Business Central. Standard Journal Standard Journals provide users with the benefit of saving transaction details and utilizing them at a later stage. Consider monthly expense payments, users will manually enter the details for the current month’s initial payment and save the journal line entries for future usage. Steps to save Standard Journal Enter the ‘Code’ and ‘Description’ to uniquely identify the journal. Users can even enable the ‘Save Amount’ toggle button to save the amounts on the journal.  Steps to Reuse Standard Journal Please note: The changes made on journal lines will not reflect on the saved template. Conclusion This feature of Dynamics 365 Business Central is very useful for users who are working with Journals that are recurring in nature. Hope this helps!

Introduction Business Central allows various levels of security that can be used to restrict User access to different features or objects. We can use Permission Sets to prevent User access to specific objects like reports or pages. For more refined, row-level authorization we can use Security Filters to restrict access to individual record based on some filters. References Using Security Filters in Business Central – Business Central | Microsoft Docs Pre-requisites Business Central OnCloud or OnPremise Configuration Suppose, you want the User to only be able to access a specific set of Customers. You can either create your own Permission Set from scratch, in which you will describe all the objects that the User will have access to or you can copy one of the existing ones by clicking on “Copy Permission Set” and then entering a new name for the permission set. Do note that you require proper permissions to make changes to Permission Sets as well. Open the Permission Set, by clicking on the “Permissions” action and Scroll to the Right. Click on the three dots next to the Security Filter field. Select the field(s) which you want to filter by clicking on the three dots next to the Field Number and then click on OK. Set a value for the filter in the “Field Filter” field. You can add as many filters as required and any Business Central filter is valid in this field (Except for wildcard characters). Once you are done, click on Close. Click on OK and add (in case there are no other permission sets and you have created your own) or replace (in case you have copied the permission set) the new permission set onto the User in the “User Permission Sets” tab of the User card. Login to the User Account and verify that only the records that match the mentioned filters are visible to the Users. Conclusion Thus we saw how to create and configure security filters in Business Central for maintaining record level security. As a side note, I would like to highlight that in Business Central, in case a User has multiple Permission Sets containing different levels of permissions for the same object then Business Central combines these Permission Sets and uses the least restrictive group of Permissions. As such if you apply a Permission Set with a Security Filter and another Permission Set without the filter on the same object, Business Central will use the one without the Security Filter as it is least restrictive.

Introduction: There can be a case where developers might need to display data from different companies in NAV or Unique view of Tables displaying unique values of a table or Joins from Tables. In such cases, developers can use the “LinkedObject” property of a table. Pre-requisites: VS Code AL Language Extension Microsoft Dynamics NAV Solution: Step 1: Go to SQL Server Management Studio and create a view of the table from where you want to display field values. Here I have created a view of Customer Table to display distinct Customer Names. And saved the view as “AdityaCustomer” Company Name as the prefix. View Step 2: Now, In NAV Development Environment create a table with the same as the view that has been created, Do not include the company prefix. And add the field with the same name of the field included in View. Table in NAV   Linked Object Property Step 3:  When this Table is run, you can see distinct Customer names in the Table. Conclusion:  This way developers can display data from Views using LinkeObject property. Hope this helps!

Introduction: In this blog, I will be attempting to highlight on Suggest Vendor Payment functionality in Payment Journals. Pre-requisites: Microsoft Dynamics Business Central Microsoft Dynamics NAV Demonstration: Last Payment Date: This date is the latest date which can be appeared on Vendor Ledger Entries for making the Payment. Entries that have Due Date or Discount Date before the Last Payment Date will be included in Suggest functionality. Last Payment Date Find Payment Discounts: Find all the Payments which will have discounts. If this field is TRUE then Suggest Vendor Payment functionality will include Payments with Discounts as well as Payments without Discounts. Find Payment Discounts Use Vendor Priority: While making payments, if you want to prepare the entries priority wise, then you will need to set the priority of Vendor under the Payments section. Use Vendor Priority   Priority field in Payment Section in Vendor Card By default, the priority is set to 0. If Vendor priority is not set which means that the Vendor Payments are to be processed in Alphabetically FCFS fashion. Available Amount: If the Available Amount is filled in which means that the maximum amount for the payments will be considered. Available Amount Skip Exported Payments: This boolean is used to skip those payments for which the Payment EFT file has been exported. This is generally used where the Payments are not supposed to be posted but the new payments are to be included in the list. Skip Exported Payments Check Other Journal Batches: This boolean field is used to skip all those payments which have already been included in the different General Journal Batches. This will avoid including duplicate payments. Check Other Journal Batches Summarize Per Vendor: This will make a single Payment per Vendor which will be applied to multiple documents. Also, this boolean will create separate payment entries for payments with different currencies. This feature cannot be used in conjunction with ‘Calculate Posting Date from Applied Entries‘ Summarize per Vendor By Dimension: This will create the entries for which the applied document will have the correct dimension. By Dimension Posting Date: Sets the Posting Date for the General Journal Lines. Posting Date is generally set to today’s date or date after the late payment date. Posting Date Calculate Posting Date from Applied Entries: Sets the Posting Date from Applied Entries based upon the Due Date of the Applied Document. Calculate Posting Date from Application Starting Document No.: Starting No. Series for the Payment Journal. This value will be set to Next No. after current Payment Journal Lines have been created in Payment Journal. This field is generally auto-filled. Starting Document No. New Doc No. per Line: This is used to create a separate Document No. for a separate entry line. When this is set to false, automatically a single Document No. is used for multiple entries of a single Vendor. New Doc. No. per Line Balance Account Type: Balance account type can be a G/L Account or Bank. Bal. Account Type Bank Account No. Used to generate only payments from a specific Bank Account. Vendor Filters: Vendor Filters are basically used to get only those payments related to a particular Vendor. Vendor Filters Conclusion: Thus, Suggest Vendor Payments can be a pretty good tool to deal with Payments where you don’t have to manually go and reconcile for the Vendor Purchase Invoices. There are a lot of variants to get the pending Payments with a lot of filters in Suggested Vendor Payments.

Introduction: Use the Update Block to update existing records in the source or target datastore. While integrating with Microsoft Dynamics NAV as a destination use the Update Merge Block to perform the Update Operation in Microsoft Dynamics NAV. The Update Merge block can configured as follows. General Tab Following Options are available under the General Tab. Change the Block Label Add Description Set Batch Processing Options Select the entity to use for this Operation. Matching Criteria Tab Following Options are available under the Matching Tab. Specify one or more fields in your source and target data to select records for this operation. Fields Tab Following Options are available under the Fields Tab. Map the required fields from your source to destination directly or based on some formulae. Note: The following fields must Hardcoded Error Handling Tab Following Options are available under the Error Handling Tab. When an operation fails — If the record cannot be updated, an error is logged. If no matches are found — If the record being processed does not match the criteria in the Matching Criteria Tab, it is not updated, and an error is logged. Errors and Warnings Tab Following Options are available under the Errors And Warnings Tab. Various Errors available are displayed. Once you have corrected the errors click on Validate button to update the Errors and Warnings Tab.

Introduction: Handling Errors is a best practice in Integration when integrating to keep a track of the Errors that occurred during Integration. The Customized Error Handling is Handy to find quick Errors to understand them and resolve as required. This approach can be extended to any Source or Destination as required. Our Scenario: Integration from SalesForce – NAV. Different Approaches to Error Handling: No. Approach Description Customizations Required Comments 1. Entity Level All errors will be logged in an ‘Error Log’ entity in Salesforce and NAV along with the error description and date & time the error occurred. 1. Custom entity ‘Error Log’ 2. Fields for ‘Error Log’ entity: i. Name [String(100)] ii. From Entity [String(100)] iii. Error Message [Note] iv. Record ID [String(100)] v. Created On Date [DateTime]   For instance, i. Name: Error while creating ‘Customer’ in NAV ii. From Entity: Customer iii. Error Message: The specified Country is not valid iv. Record ID: Cust123 v. Created On Date: 08/07/2018   Example:    2. Field Level If an error occurs for a record during integration, the error description will be stored in a custom field on the record in Salesforce or NAV. A custom field ‘Error Description’ will have to be created on the form of all required entities. Field: Error Description: [Note]   For instance, when you open a Customer ‘Cust123’, Error Description: The specified Country is not valid   Example:

Microsoft Dynamics Nav Integration is one of the most popular ERP solutions that most of the medium and large enterprises use today. It is an ERP solution that is not only easy to learn but is easy to learn and implement. Your staff is going to become a lot more efficient when they use this ERP solution.  Microsoft is one of the best companies in the world for all the right reasons. This software contains some of the best and unique features that will not only raise the productivity of the staff but will also improve your performance. But, if enterprises want to enjoy the benefits that come from this ERP solution, they need to plan on upgrading Dynamics NAV to a cloud-based environment. Introduction: Working with failed Scheduled Jobs can be a tiresome process. This is exactly the case where one of my clients has an Invoicing & Payment Jobs which run once a day and Job Queue Entries fail to trigger these Jobs. No Errors in the Logs, No Execution Entry, Simply No Way of Figuring it out as to why Job didn’t trigger. Contacting Microsoft Support, they are asking to simply Upgrade the Application to the latest version. Which is not a preferred option as the database size is around 200GB. Let’s see how to resolve this in a smarter way. Pre-requisites: Microsoft Windows Task Scheduler Microsoft Windows Powershell Microsoft Dynamics NAV(Administration Module for PowerShell & Development Environment) Books & References: https://docs.microsoft.com/en-us/powershell/module/microsoft.dynamics.nav.management/?view=businesscentral-ps Demonstration: 1. Building Objects to Run through a Codeunit: As you know that Job Queue Entries support Reports and Codeunits and NAV Administration Module only supports Codeunit. So, in order to make it work, create a Codeunit to execute all the Reports and code units. 2. Creation of PowerShell Script: This PowerShell Script executes with the help of NAV Administration to Run the Codeunit. Prior to running the script, you need to set the Execution Policy. Syntax: Invoke-NAVCodeunit <Codeunit No.> – ServerIntance <ServerInstanceName> -CompanyName  <Company Name> -Force 3. Setting Up Task Scheduler Triggers: By Setting up the Triggers, you can decide recurrence to execute the Codeunit. It can be Hours, Daily, Weekly, Monthly, One-Time or Infinite. You can also set the time for precise execution. 4. Setting Up Task Scheduler Commands: Whenever we execute the PowerShell Script through CMD, we run the commands as follows. Command: PowerShell.exe <PS Script File Path> Here, we pass the PowerShell.exe into the script and PS Script File Path as a Parameter. Conclusion: Thus, using NAV Administration Module, Power-Shell and Task Scheduler I was about to replicate Job Queue Entries functionality. Although this works perfectly for NAV and Business Central – On-Premise, it works for Business Central on SaaS. In my upcoming blog, I’ll also show we can achieve this. Hope you guys find this blog useful 😇