olisterr.tech | Blog on Dynamics 365 Business Apps, NAV / Business Central, Power Platform and Azure

  Introduction: With Business Central getting stable, Microsoft is adding more features in order to make the lives of Users easier. One such feature I would like to discuss is the Standard Journals in General Journal. Pre- requisites : Microsoft Dynamics Business Central (OnPremise or SaaS) Understanding of General Journals Books & References: https://docs.microsoft.com/en-us/dynamics365/business-central/ui-work-general-journals Demonstration: 1. Open General Journal and create Entries: You can do a search in Business Central for General Journal and select General Journal Batch which will open the General Journal. You will need to add Journal Entries as usual. Basically these entries are the ones that you will be repeating over a period of time. For Eg: Recurring G/L to G/L Transfers Create General Journal Entries 2. Save Entries with/without Amounts: On the General Journal, click Save Entries in General Journal which will open a form to ask you the basic details. Open General Jour

Introduction: When you setup a Business Central Server on Azure for Development / Non- production activities and do not have Disaster Recovery backup setup, there are chances that your VM might not boot up. Most of the times there are issues with billing, networking or even Windows Update and still can be recovered through Azure Support. However the situation I face was Blue Screen of Death and there was lower chances of booting up. Pre-requisites: Fundamental understanding of Azure Microsoft Azure Subscription  Demonstration: 1. Create Disk Snapshot: Generally installations can be done again. However Databases are something important for you. Hence, you will need to attach your crashed VM Disk Drives as auxiliary Disk Drives to a working VM. For existing Drives, you will need to make a Disk Snapshot from the existing Disk Drive. Go to VM > Disks > Select Disk Drive > Make Snapshot. Disk Drive you would like to backup Create Disk Snapshot Create Disk Snapshot > Provide Disk

Introduction: In our previous blogs, we discussed setting NAVUserPassword and Single Sign-On Authentication in Business Central. In this blog, we will be working on setting Windows Authentication in Business Central On-Premise. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: https://www.olisterr.blogspot.in/2020/03/how-to-setup-single-sign-onsso-for.html https://www.olisterr.blogspot.in/2020/03/how-to-setup-navuserpassword-with-ssl.html Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Instance - Ports and Service Account - Business Central Administration PowerShell Command:  New-NAVServerInstance    -ManagementServicesPort <ServicePort>    [-ClientServicesPort <ServicePort>]    [-SOAPSe

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: https://community.dynamics.com/nav/f/microsoft-dynamics-nav-forum/261301/nav-2018-web-client-an-error-has-occurred https://community.dynamics.com/business/f/dynamics-365-business-central-forum/421987/error-something-went-wrong-an-error-has-occurred-azure-ad-tenant Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta

Introduction: I'm sure with the dawn of Business Central Online, its been so easy to directly get users from Office 365 and the only part that you are remaining with is setting up User Permissions. After SSL & SSO is setup in Business Central On-Premise, the question comes as how to add Users and connect to Azure AD. To get how to setup SSL and SSO refer the links below SSL Setup -  https://olisterr.blogspot.com/2020/03/how-to-setup-navuserpassword-with-ssl.html SSO Setup -  https://olisterr.blogspot.com/2020/03/how-to-setup-single-sign-onsso-for.html Pre- requisites : Microsoft Dynamics Business Central On-Premise SSL Setup SSO Setup Understanding of  Office 365 Understanding of Azure AD Books & References: https://olisterr.blogspot.com/2020/03/how-to-setup-navuserpassword-with-ssl.html https://olisterr.blogspot.com/2020/03/how-to-setup-single-sign-onsso-for.html Demonstration: For SSO Authentication -  1. Search for Users in Global Search and select the Users (Administrat

Introduction: Since Business Central's inception, Subscription-based licensing is in use. While implementing LS Central, I noticed that this cannot be simply based on Subscription-based licensing because there are multiple shared terminals between multiple staff members. The worst part is that not all users are logged in at the given time which means the efficiency is closed to 50%. This issue can be resolved by handling device-based licensing whereby the license is paid only for the number of devices used as long as the registered device logs in. This blog will demonstrate how to enable device-based licenses for Business Central. To understand where Device-based License is used, refer to https://www.solsyst.com/post/business-central-device-license-capabilities-when-to-use Pre- requisites : Microsoft Dynamics 365 Business Central  Demonstration: 1. User setup for Device-based License: 2. Registering your Device MAC Address: To get the MAC Address of the Device, open CMD and run the

Problem Statement: Disclaimer:  This blog is only applicable for Business Central On-Premise Version. If you are stuck in the same issue, try this at your own risk.  I had installed  Business Central v14 (Spring 2019) On-Premise with LS Retail . In this, Business Central comes with a ready made setup to connect with VS Code. As I restored the DB given by LS Retail, I could no longer connect to VS Code. This could be a potential case of  Running C/SIDE and AL Side-by-side  or customising on top of LS Retail. Despite all the configurations being correct in project's app.json and launch.json, I could no longer connect to Business Central, I  couldn't download any Symbols  and I  couldn't publish any Extension  to Business Central.   App.json and Launch.json I checked all BC Administration setup for Development and it seemed to be perfectly fine. I had  Enabled Development Endpoint ,   Development Endpoint Port was 7049 ,  Target was set to Internal ,  Ena