Introduction:  As a business owner, you might have come across a situation where you want to upgrade your current systems with renowned ERP solutions available on the market. One of the ERPs you would consider is Microsoft Dynamics. However, even choosing this would require a lot of brainstorming from all decision-makers because Microsoft Dynamics comes with two ERP platforms, i.e., Dynamics 365 Business Central and Dynamics 365 Finance & Supply Chain. I assume this brainstorming itself would have probably landed you on this article. Let’s dive into the key differences and use cases for each platform. Hopefully, by the end of the article, you will be able to make a decision and choose the right platform for your business.  Below are the key factors differentiating Dynamics 365 Business Central and Dynamics 365 Finance & Supply Chain: Company Size: When determining company size, the usual factors that are considered are revenue and employee count. The definition of which can change based on the country you are located in. Here, for reference, we would consider the following: – Revenue: a. SME: Having revenue between 0 and 1 billion USD. Business Central is ideal for this size of company. b. Large companies: Having revenue above 1 billion USD. Finance and Operations is the ideal platform for large organizations. – Employees: a. SME: having employees between 0 and 500. b. Large companies: having more than 500 employees. Number of Entities: If your company has multiple legal entities in multiple geographical locations across the world,a. Business Central is ideal for companies with a single legal entity or multiple legal entities in the same country. Business Central allows you to create and manage individual products and accounts for each legal entity; however, it cannot be managed centrally. b. Finance and supply chain are ideal for companies with multiple legal entities across the world. Finance & Supply Chain allows you to manage products and accounts centrally and release them centrally to each legal entity across the world. Business Operations: Does your company have streamlined and simple operations? a. Business Central can handle operations for companies with streamlined and simplified operations that do not require very detailed data capture or sophisticated reporting. b. Finance & Supply Chain captures detailed data, covers a lot more processes than Business Central, and hence can provide robust and detailed reporting. Future Growth: It is also important to consider what the growth plans are for your company. If you currently have 2–3 legal entities, you may be tempted to go with Business Central, as it comes with low implementation and operating costs, ease of use, and faster implementation timelines. However, ERP projects are not done frequently, and it is important that you consider future organizational plans. Let’s say you intend to expand over the next three to five years into multiple different geographical areas. You should think about finance and supply chain as your organization’s go-to platform since this will be a big, long-term investment. You might want to consider the following factors while making the decision: – Licensing: a. Since finance and supply chain are for large companies, they come with a minimum licensing requirement of 20 licenses. b. Business Central is perfect for small and medium-sized businesses (SMEs) because it only requires one license and has no minimum licensing requirements. – Implementation timelines:a. Finance and Supply Chain has a typical implementation timeline of 6 months or more, considering the size of the implementation and global rollout.b. Business Central can be up and running in 3–6 months.    Conclusion:  Choose Business Central if: You’re an SME seeking an easy-to-use, all-in-one solution with a lower upfront and operating cost.  Choose D365 Finance & Operations if: You’re a large enterprise requiring extensive functionalities, deep customization, and global capabilities.  We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction: The 2024 Wave 1 release of Microsoft Dynamics 365 Business Central introduces a new feature called Page Scripting. This tool is designed to enhance User Acceptance Testing (UAT) by allowing users to record and replay their actions within the Business Central. This capability streamlines the UAT process by automating repetitive tasks and ensuring consistency across tests. Capabilities and Usage: The Page Scripting tool, records user interactions such as opening pages, entering data, and navigating through the system. These interactions can be saved and replayed, making it easier to validate the system’s behavior under various conditions. The tool records actions in a YAML file format, which can be shared and reused, promoting collaboration and efficiency. Let’s get started with how page scripting works: – Setup: To use the Page Scripting tool, users must have specific permission sets assigned. – Once these permissions are in place, users can access the tool by navigating to Settings and selecting the Page Scripting (Preview) action. The tool pane appears on the right side of the screen, allowing users to start a new recording or open an existing one. – When the user clicks on Page Scripting action, following screen opens up: – In that, user have an option to start a new recording or open existing recording. – User can start a recording by clicking on “New recording” or “Start new” button. – When user clicks on ” Start New/New recording” following page displays: – When new recording is started it captures every user action and input, including interactions with custom or third-party extensions. Users can track their steps, such as opening the Customer List page, selecting a customer record, and entering new sales prices. During the recording, users can delete the last recorded step if needed and can stop and resume recording as necessary. For Example: – Once all the steps are completed, user can stop the recording and save the file in YML format. – If the user wants to replay the recording, then simply user can click on open recordings, select the saved file and all the recorded script will appear on the right screen. – A recording can then be played, and all the recorded actions are executed in the web client. User will see an indicator if an action is succeeded or not as shown below: – User can Click on “Play” action, the system will automatically run the whole script and indicate (a green tick) if successful as shown in above image. Conclusion: In brief, the Page Scripting tool in D365 Business Central enables advanced customization, allowing users to optimize workflows, enhance user experience, and drive efficiency within the system. This tool offers valuable flexibility for businesses to tailor their operations to their unique needs and goals. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction  Dynamics 365 Project Operations (PO) is a project management application within the Dynamics 365 suite. It is designed to manage project-related tasks, schedules, resources, and budgets. While they may include some financial functionalities, they often lack the comprehensive financial management capabilities that dedicated financial platforms offer.  In this article, we will explore several functions that Project Operations (PO) cannot perform as effectively as financial platforms like QuickBooks (QB) or Dynamics 365 Business Central (BC).  We will also discuss how to bridge this gap and create a seamless integration between Project Operations and these financial platforms.  Let’s first look at what Project Operations falls short of and what financial platforms like QuickBooks or Dynamics 365 Business Central can offer.  Accounting Functionalities  General Ledger Management: Financial platforms provide robust general ledger management, allowing for detailed tracking and reporting of all financial transactions across the entire organization.  Accounts Payable and Receivable: They manage accounts payable (AP) and accounts receivable (AR) efficiently, including invoicing, bill payments, and collections.  Tax Compliance: Financial platforms are equipped with tools to manage tax calculations, filings, and compliance with local and international tax regulations.  Financial Reporting: Financial platforms offer extensive reporting capabilities, including profit and loss statements, balance sheets, and customizable financial reports.  Audit Trails: Financial platforms maintain detailed audit trails of all financial transactions, which are crucial for internal audits and external regulatory audits. To leverage the Project Management features of Project Operations and the above-discussed features of financial platforms, businesses often choose to integrate both systems.  Integration Approach  Custom integration offers the utmost flexibility when connecting Project Operations with QuickBooks or Business Central. Several key considerations and entities are important to ensure a seamless integration: Data Mapping:  Tables: Identifying the key entities (Tables) such as projects, expenses, invoices, customers, vendors, contacts, and accounts that need to be synchronized between project operations and financial platforms.  Mapping: Map the fields and attributes of these entities between the two systems to ensure accurate data transfer and synchronization.  Tip: The best practice is to create mapping Excel for maintaining the table and column mappings between the systems.   Chart of Accounts (COA):  Chart of Accounts: Proper alignment between the chart of accounts in Project Operations and the financial platforms is necessary to facilitate accurate financial reporting and reconciliation.  Tip: Creating custom tables for your Chart of Accounts (COAs) and designating the financial systems as the source of truth for COAs is recommended. This approach offers flexibility to associate COAs with expenses, materials, roles, etc.  API Integration:  API Access: Check if the financial platforms offer APIs for integration.  Integration Points: Determine the integration points where data will be exchanged between the two systems, such as project creation, expense tracking, invoice generation, and payment reconciliation.  Data Flow:  Data Direction: Define the direction of data flow between Project Operations and financial platforms, ensuring consistency and integrity of data. The source and the target systems should be defined.  Real-Time Sync: Decide whether data synchronization will occur in real-time or through scheduled batch processes to meet business requirements. Currency:  Currency Conversion: Consider currency conversion requirements when dealing with contracts or transactions in multiple currencies.  Error Handling and Logging:  Error Handling: Implement mechanisms to handle data validation errors, inconsistencies, and exceptions during data transfer between systems.  Logging: Maintain logs of integration activities and errors for troubleshooting, audit trails, and compliance purposes.  Security:  Authentication: Implement secure authentication mechanisms to ensure data privacy and integrity during data exchange between systems.  Access Control: Define roles and permissions to restrict access to sensitive data and functionalities based on user roles and responsibilities.  Testing:  Testing: Set up a dedicated testing session to validate the integration setup, data mappings, and synchronization processes before deploying to production.  Integration process flow diagrams:  Create a process flow diagram for all the entities, for example below, is an integration process flow diagram for integrating Accounts, Contacts, Vendors from Project Operations to Quick Books.  In conclusion, while Project Operations is essential for managing the operational aspects of projects, it lacks the depth and breadth of functionalities offered by dedicated financial platforms.   Financial platforms provide accounting, regulatory compliance, advanced financial reporting, cash flow management, and more, which are crucial for the overall financial health and strategic planning of an organization.   Integrating these platforms with Project Operations tools leverages the strengths of both, ensuring efficient project management and robust financial oversight.  Here is our featured Customer Success Story:  Armexa, a leading US-based Industrial Cybersecurity Company, partnered with CloudFronts for Services Automation with Microsoft Dynamics 365 Project Operations and Business Central.   We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction By default, Business Central comes with 80GB of storage capacity across three sandbox environments and 1 Production Environment with an additional 3GB/Premium License, 2GB/Essential License, 1GB/Device license. These storage limits depending on your Business volume may run out if the data is not managed properly. Business Central now comes with a one stop view where you can manage (compress or delete) the entries to reduce storage usage – “Data Administration.” Pre-requisites Business Central Cloud/On Prem References Manage Storage by Deleting Documents or Compressing Data – Business Central | Microsoft Learn Configuration In Business Central, we’ve had the option to view the capacity usage from the Admin Center for a while now. Recently, they’ve also added a one stop view to check and manage the capacity usage – Data Administration from within Business Central itself. It can be found directly from the global search. The first time we open this we are greeted with an empty view, the data is loaded after we click on refresh to load the latest data. You can also configure it so that the data is loaded automatically in the background every so often. Here, we get the options for Data Clean up where we can delete data that isn’t required anymore. All of the below options, open a similar processing report where you can set filters which are used to delete the records as needed. The “Delete Detached Media” opens another page which I’ve discussed in depth in another blog. The second action groups hold actions which are meant to compress the ledger entries which can drastically reduce the storage space used. It is important to note that you can only compress entries which are older than 5 years by yourself which belong to Fiscal years that are closed and the entries themselves are closed (Open is set to false). You can configure the compression such that there is one entry per day, one entry per week, one entry per month, one entry per quarter, one entry per year or one entry for the period that is defined for compression. You also have the functionality to delete empty registers from here. If these individual actions seem to be overwhelming, Microsoft also provides for a Data Administration wizard which simplifies this process and allows you to manage the capacity via a wizard. Conclusion Thus, we saw how we can use the standard data administration tools to manage capacity of Business Central environment which can help the system run much more efficiently in terms of both performance and costs. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction:  Many Businesses supports buying and selling items with different unit of measures. How to configure this in Business Central without showcasing your inventory in decimals. Let’s take an example: We will be buying the goods always in dozen whereas we can sell the items in PCS or CARTONS. Steps to achieve the goal: 2. Once the base unit of measure is set to PCS. Go to the Item Unit of Measure page by click on Related-> Unit of Measure. 3. By default PCS line would be set to 1. Add new line enter DOZEN and next right 6 which means 1 dozen has 6 PCS. 4. Next line add CARTONS and enter the qty per unit of measure as 72. which means 1 Cartons has 72 PCS in it. 5. Once the above lines have been set. Let’s pass Item journal where will be increase the inventory by dozen and sell the items in PCS and CARTONS. Ideally the inventory would be shown without any decimal value. 6. Below is the explanation how system would calculate into PCS as when you buy and sell in different items. 7. Purchase 100 dozen which is 600 PCS. This would be converted by Business Central itself. As we have defined 1 dozen as 6 PCS. 8. Sales 7 Cartons which is 702 PCS. This would be calculated by Business Central itself as per the Item Unit of Measure configuration where 1 cartons is 72 PCS. 9.Once the above transaction is posted the inventory would be whole value without any decimal. Conclusion:    Thus, we saw how we can use alternative Unit of measure in Business Central. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

While going through some sales documents, I noticed that the page that appears when I click on “Show Details” in the notification for low inventory has been updated! When we click on “Show Details” now, we’re taken to the page named “Item Availability Check”. Furthermore, it includes options to directly create a Purchase Order or a Purchase Invoice from this page.  If a Vendor is specified in the “Vendor No.” field of the Item Card, the Purchase Order/Invoice is automatically generated with that Vendor. In the scenario where multiple vendors are selected in the Item Vendor Catalog instead of the Vendor No., all the vendors are displayed, and the one selected by the user is utilized to create the Purchase Order/Invoice. In both cases, the Purchase Line will reflect the shortfall as the Quantity. If the Item has any substitutes available then the “Substitute Exists” indicates the same and clicking on it opens the Item Substitutions page. Further, if you click on the “All Locations” then the “Item Availability by Location” page is opened. That’s all! Just wanted to share something new I learned recently. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction Error handling is an important concept in every technical field.  It helps programs deal with unexpected problems and mistakes smoothly.  It makes sure software works reliably and doesn’t crash unexpectedly.  Error handling also helps developers find and fix issues quickly, making the software better for users. Plus, it gives users clear messages when something goes wrong, making their experience smoother. It shows that the team has considered the scenario and has measures in place for it indicating a well designed solution. Microsoft has an amazing document which lists the things to keep in mind for writing resilient code. In Business Central, we have try functions to handle errors and error function to show those errors to the Users.  In this blog, we’ll learn how we can enhance the error messages so that the Users can resolve the errors themselves or at the very least we can point them towards where the error is. Pre-requisites Business Central OnPrem/Cloud References Actionable errors Try Methods for Error Handling Robust Coding Practises Error Info – Business Central Docs Explanation Before we get to the code, let’s set a little context. For Error Handling, Microsoft has two categories in Business Central, ErrorInfo is a data type used for error handling and reporting.  It can be used to hold information about errors that occur during the execution of code. It has additional properties and actions that can be used to define it’s behavior to the end-user. The ones that are most useful as – The “Add Action” procedure takes a codeunit and a method name as input. To pass input into this procedure, we add an “ErrorInfo” object as a parameter to the function and if we want to specify some details of the record where the error is happening or where the fix is to happen, we can use the following procedures. The “Add Navigation Action” only takes a method name as an input. So, to tell the action which page and which record to open we have the following procedures. If you are passing the Page No. and System Id to the procedure which handles the error then the same can be accessed there as well. Code Here, I’ve taken a sample scenario where the value of one field depends on the value of another field on the Sales Order. Basically ;-   I’ve set it up so that these validations are triggered when the Sales Order is posted. And the same thing goes for the “Not Blank” scenario so I’m not writing it for now. So, if I try the second scenario where Type is “Blank” and Field has some value then we get the following error message. If I click on the “Copy Details” I can see the detailed message that I added for this Error Info. If I click on the “Make Mandatory Field Blank” action then I can make the “Some Important Field” as blank. The code behind the action – “Make Mandatory Field Blank” is as follows-  I’ve used messages to confirm that the values that I passed during the origin of the error are flowing into the procedure. Here are the messages –  Now, some of you might be wondering, if this was a error message where one field was dependent on another then it should’ve been a validation. And yes!  That is correct and here is how it would look. Here, I’ve used both “Add Action” and “Add Navigation Action” on the ErrorInfo. For the Parameters, all of the parameters are pointing to the Customer. This opens the Customer Card for the specified Customer. Conclusion You can refer the “Actionable Errors” documentation for the best practises and patterns for which type of actionable error to use and where to use it. Thus, we learned how to utilize actions within error messages in Business Central to assist users in resolving errors more effectively. We hope you found this article useful and if you would like to discuss anything you can reach out to us at transform@cloudfronts.com. 

Introduction: “Wait” typically refers to the amount of time during which a database session waits for an event to complete before it can proceed with execution. Waits can arise for many reasons in a database system, and understanding them is important for  tuning and optimizing performance. References: Explanation: Waits, in SQL, are broadly categorized into three categories: Resource Waits: These happen when a worker needs access to a resource like data or system resources, but it’s not available because another worker is using it.Examples include waiting for locks, system latches, or for data to be read from the network or disk. Queue Waits:  Occur when a worker is waiting for a task to be assigned to it.Think of it like waiting in line for a job to do.This commonly occurs with system tasks like deadlock detection or cleaning up deleted records.Even if there’s no immediate task, workers might still check periodically. External Waits:  This occurs when a worker is waiting for something outside the SQL Server environment to finish, like a call to an external procedure or a query to a linked server.It’s important to note that just because a worker is in external wait doesn’t mean it’s idle; it might be actively running external code. In context of Business Central, we see the following “wait” types: Buffer IO: This type of wait occurs when a database session is waiting for data to be read from or written to the buffer cache, which is an area of memory used to cache data pages from disk. Buffer Latch: Buffer latch waits happen when a session is waiting to acquire a latch on a buffer in memory. Latches are used to protect access to in-memory data structures, and buffer latch waits can occur when multiple sessions are contending for access to the same buffer. Compilation: Compilation waits occur when a session is waiting for a SQL query or stored procedure to be compiled and optimized by the database engine. CPU: CPU waits occur when a session is waiting for CPU resources to become available for query processing. Idle: Idle waits occur when a session is not actively performing any work and is waiting for something to do. Latch: Latch waits, as mentioned earlier, happen when a session is waiting to acquire a latch on a data structure in memory. Lock: Lock waits occur when a session is waiting for a lock on a resource that is held by another session. Memory: Memory waits occur when a session is waiting for memory resources to become available. This can include waits for memory allocations, deallocations, or other memory-related operations. Network IO: Network IO waits occur when a session is waiting for data to be sent or received over a network connection. Other: This category typically includes waits that don’t fit into the other specific categories listed. Other Disk IO: This is similar to Buffer IO waits but encompasses other disk-related operations beyond just buffer reads and writes. Parallelism: Parallelism waits occur when a session is waiting for other parallel threads to complete their tasks. Preemptive: Preemptive waits occur when a session is waiting for an external operation to complete, such as an operating system call. Service Broker: Service Broker waits occur when a session is waiting for a message to be sent or received via the Service Broker feature in SQL Server. SQL CLR: SQL CLR waits occur when a session is waiting for a Common Language Runtime (CLR) operation to complete. Tran Log IO: Transaction Log IO waits occur when a session is waiting for data to be read from or written to the transaction log. Transaction: Transaction waits occur when a session is waiting for a transaction to complete. User Wait: User waits are general-purpose waits that occur when a session is waiting for some user-defined event to occur. Worker Thread: Worker thread waits occur when a session is waiting for a worker thread to become available for query processing. Conclusion: Thus, we saw how we can use the “Database Wait Statistics” in Business Central to identify performance bottlenecks in the system. We hope you found this article useful and if you would like to discuss anything you can reach out to us at transform@cloudfronts.com. 

Introduction For any Business Application, database replication is a necessity for the application to be highly available, fault tolerant and performant without any data throughput issues. Business Central too follows the database replication utilizing a technique known as “Read Scale Out” or “Leader/Follower or Master/Slave Replication Architecture”. Basically, the business operations(Codeunits, Pages, POST/PUT/DELETE API calls) which create the data in the system are relatively quick as compared to Analytical operations (Reports, Queries, GET APIs calls)which read a whole bunch of data from a lot of tables at once. So, in this case, performing both business and analytical operations on the same database can cause performance issues as tables can be locked by an analytical operation while a business operation tries or access or modify that data. A solution for this is using multiple copies of the database in a leader follower architecture.All the write transactions are directed towards the leader database which are then forwarded to the follower databases.All the read transactions can be forwarded to either the leader or the follower database. Please note that this all only happens for Production Environments. Sandbox environments only have the primary database. Side Note  If you’re wondering what happens when a User tries to read from a follower database before the leader database was able to send the updated information there (This is called a stale replica).  This is an accepted risk when using this architecture. According to CAP Theorem only two of the three properties, Consistency, Availability and Partition Tolerance can be guaranteed. Out of these, partition tolerance has to be tolerated as network failures are inevitable so most systems have to choose between Consistency and Availability. In most cases, RDBMS systems choose Consistency over Availability (as does Business Central) and most NoSQL databases choose Availability over Consistency. Pre-requisites Business Central Cloud/OnPrem References Explanation Setting the property DataAccessIntent to ReadOnly doesn’t guarantee that all the operations that a particular object does are going to be routed via the “replica database”. For example, consider a case where we are using a processing report to update a field on the Item table based on the calculations done using a Query object. Here, when the operation started, given that the processing report intents to update the Item table, the operation was forwarded into the Primary database, now when the Query is executed to fetch the generate the necessary value, the database is still going to be the Primary database. To summarize, the database is not switched in the middle of a transaction. For API Pages where we are only going to be fetching the data from Business Central, we have to set the API page’s Editable property as false and only then we can set the DataAccessIntent to ReadOnly.We don’t have this property for any other page types. For Reports, we can set the DataAccessIntent property directly and if it is a processing report that tries to make any modifications to the data then we end up with a run-time error. For Queries, we can set the DataAccessIntent property directly as well with the same conditions as the Report object but in effect, the only time queries benefit from the “replica database” is if they are used directly as APIs. Almost all the ODATA GET requests are directed to the “replica” database by default in Business Central on Cloud. In the On-Premise Environment, we have a setting “ODataReadonlyGetEnabled” that controls this behaviour. Further, there is a list page in Business Central “Data Access Intent List” which can be used to modify the Data Access List of any Page, Query or Report object. The Default Value indicates that the object should use the pre-defined value defined in AL. The same rules as above are followed when we update the “Data Access Intent” values in the Data Access Intent List page. Conclusion: Thus we saw how Business Central architecture uses the “read scale out” method to ensure consistency and availability and how we can leverage those to boost our application’s performance. Happy Coding!

Introduction: Microsoft Dynamics 365 Business Central (formerly known as Microsoft Dynamics NAV) is a comprehensive business management solution that helps organizations streamline their financials, supply chain, sales, and customer service processes. It offers robust features for managing various aspects of your business, from inventory control to financial reporting. In this blog post, we’ll focus on the steps to download and install Business Central on-premises within a virtual machine. Whether you’re a developer, IT administrator, or business user, understanding this process is essential for setting up a local environment to explore and work with Business Central. Pre-requisites: Steps: 2. Choose the region for the business central 3. Extract the downloaded file. 4. Go to the extracted file and click on setup. 5. Choose Advanced Installation Options -> Choose an Installation Option -> Custom. 6. Make all the listed components available (Run from My Computer) or (Run all from My Computer). 7. Make the necessary changes. 8. Go to Azure Portal and assign the DNS Name in Azure Portal. 9. After the successfully installation, go to Windows PowerShell ISE -> “Run as Administrator” and execute the below commands line by line. Set-ExecutionPolicy unrestricted -Force Import-Module ‘C:\Program Files\Microsoft Dynamics 365 Business Central\230\Service\NavAdminTool.ps1’; Get-NAVServerConfiguration -ServerInstance BC230 Set-NAVServerConfiguration -KeyName EnableDebugging -KeyValue true Set-NAVServerConfiguration -KeyName DeveloperServicesEnabled -KeyValue true Restart-NAVServerInstance -ServerInstance BC230 Get-NAVServerUser BC230 Set-NavServerUser -Company ‘CRONUS International Ltd.’ Note: Upon executing the New-SelfAssingedCertificate command, a Thumbprint will be generated. Please retain the thumbprint ID for your reference. New-SelfSignedCertificate -DnsName “www.shubhazure.eastus.cloudapp.azure.com” -CertStoreLocation “Cert:\LocalMachine\My” 10. After creation/installation of Certificate, Go to Manage Computer Certificates > right-click on the Certificate > All Tasks>Manage Private Keys > Add NETWORK SERVICE and allow access to all the users and copy the certificate to Enterprise Trust, Trusted People, Trusted Publisher and Trust Devices folder. 11. Go to IIS Manager in that BC230 -> click on Browse “:8080 (http)”. 12. Change Credential Type and Add Thumbprint Set-NAVServerConfiguration -KeyName ServicesCertificateThumbprint -KeyValue Set-NAVServerConfiguration -KeyName ClientServicesCredentialType -KeyValue NavUserPassword 13. Change the Credential Type in navsettings.json file: This tells Business Central Clients to change the CredentialTypes for the Client. Goto C:\inetpub\wwwroot\<WEB SERVER INSTANCE>\navsettings.json 14. Go to Users in Business Central, insert the Password: 15. Binding your Web Server Instance with SSL / Self-Signed Certificate in IIS: 16. Restart the Server Instance in Business Central Administration and Webserver instance in IIS.  Result After inserting the credentials, you will get access to Business Central. Conclusion Thus, in this blog we saw how to download Business Central (BC230) on Virtual Machine. We hope you found this article useful and if you would like to discuss anything you can reach out to us at transform@cloudfonts.com.