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

Introduction: In this blog, I'm attempting to capture the LS Central - POS installation process on Local Machine. This blog has nothing to do LS Central - Server Setup for POS. LS Retail / LS Central - On Premise POS Pre- requisites : LS Central Installed on Server SSL Setup on LS Server (https://www.olisterr.tech/2020/03/how-to-setup-navuserpassword-with-ssl.html) LS - POS Installer Business Central - On Premise Installer Demonstration: Once your LS Retail / LS Central POS is setup on the main server. Just prior to Go-Live, you will actually have to install this POS on multiple systems and connect these POS to the main server with LS Retail / LS Central. 0.Preparation: Prior to actually installing Business Central On-Premise Windows Client, you need to make sure that you're able to ping the target with the correct Port number. For this I made use of PS-Ping tool.  PSPing - IP Address: Port If you're unable to PS-Ping the correct IP with Port number, simply check the Advan

07/10/2020 - Update on Self-Signed Certificate Setup Process for NAV / Business Central  As per my previous post on setting up NAVUserPassword here Reference:  https://community.dynamics.com/nav/b/dynamicsnavcloudfronts/posts/how-to-login-windows-client-and-web-client-using-navuserpassword-authentication-in-microsoft-dynamics-nav If you have created a Certificate using the above PowerShell command and it gives error while starting the NAV / BC Instance with the error as follows: ******************************************************* Server instance: DynamicsNAV100 Tenant:  <ii>The service MicrosoftDynamicsNavServer$DynamicsNAV100 failed to start. This could be caused by a configuration error. Detailed error information: System.ArgumentException: It is likely that certificate 'CN=navision.southeastasia.cloudapp.azure.com' may not have a private key that is capable of key exchange or the process may not have access rights for the private key. Please see inner exception for

Introduction: I had a requirement where the Web Services / APIs in NAV and Business Central On-premise needed to be exposed outside the VM to be consumed by third-party applications. Also, this blog is a continuation of my previous blogs on NAVUserPassword and Single Sign On(SSO)   In this blog, let us see how to expose the Webservice / API URLs outside the server and consume them. Pre- requisites : Microsoft Dynamics Business Central On-premise Static IP assigned to the Server DNS configured with SSL or Self-signed certificate. Demonstration: 1. Changes to Business Central On-Premise / NAV Administration Console: Inside the Administration Console, you need to make sure that either you Business Central already has a way to be authenticated with the DNS link that you have provided. You can refer to my blogs   NAVUserPassword  and  Single Sign On(SSO)  for this After that make sure you enable SSL and change the Base URL to '<https://YourDomain:Port/ServerInstance>'. Also,

Introduction: Today, I found something interesting in Business Central. When you open Users > Select User > Web Service Key Field, you will notice that it is either blank, has some value, or has a string of  '*' symbols Pre- requisites : Microsoft Dynamics 365 Business Central Demonstration: 1. When you open a current logged in User: You will notice that the Web Service Key is <BLANK> if not configured. If the Web Service Key is configured then you will be able to find the key. You can triple-click to select the whole key.           Current User 2. When you open a different User from currently logged in User: You will notice that the Web Service for a different User will be '**************************' after version 16.5 and above. Which also means that even if you copy the Web Service Key to the clipboard you will receive the same '****************' character. Earlier this wasn't the case, instead, we were able to simply check the keys for diffe

Introduction: Have you ever got into a requirement, where you are needed to actually execute the logic separately for different client types? Well, this blog is just going to discuss the ClientType DataType and different ways of getting ClientTypes and how to use it in your code. Pre- requisites : Microsoft Dynamics Business Central Online AL Language Extension VS Code References: https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/methods-auto/session/session-currentclienttype-method https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/methods-auto/session/session-defaultclienttype-method https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/methods-auto/clienttype/clienttype-option Demonstration: ClientType: In order to understand how to use ClientTypes, we need to understand what ClientTypes represents. ClientType is an Option based DataType introduced in Business Central. That is in order to get

 Announcement: Business Central v17 - Wave 2 2020 Release is out In order to sign-up for Business Central v17 -  Wave 2 2020 For Online Tenants refer the steps below: 1. For existing subscription: If you are an existing client, you can simply goto Business Central Admin Center > Create a Sandbox as per the screenshot below.   Business Central - Wave 2 2020 - Release - Creation of Sandbox After you have created a Sandbox, you can play around and check how the new features work. Business Central - Wave 2 2020 Release In order to upgrade your Production to v17, go, and simply schedule your upgrade data and select the update window. 2. For existing new customers: Whenever you sign-up for a Business Central Environment through https://trials.dynamics.com, you will by default receive the latest Wave 2 2020 Release signed up. https://trials.dynamics.com - Signup After the clicking 'Get Started' this you will receive the following screen Environment setup Although I didn't recei

Introduction: In this blog, I'm going to demonstrate the newly available Business Central Admin Center coming up in October for the 2020 Release Wave 2  Pre- requisites : Business Central Admin Center Demonstration: 1. Changes to Business Central Admin Center: After you login in Business Central Admin Center, you will observe a couple of changes in the Admin Center on the Main Screen directly. The changes are missing actions, additionals sections. 2. Changes on Environment Card Page: After selecting the environments, you will notice key things such as renaming the environment. 3. Update Settings in Business Central Environment: When you click Update Setting, you have the ability to schedule Update Windows and Date. 4. Renaming Business Central Environment: While this was an easy one, the best one so far is the 'Renaming' feature  5. Delete Action feature moved to Environment Card:   There is another one where the actions on the Environments List Page is moved to the card pa

  ANNOUNCEMENT : Preview Environments for Business Central 2020 Release Wave 2 is out. Source: https://www.yammer.com/dynamicsnavdev/threads/851455199543296 To set up your preview: https: //docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/preview-environments To get access to collaborate: https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/preview-environments To understand the timeline for the roadmap on major updates for Business Central: https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/update-rollout-timelime Procedure: To sign-up the Sandbox for Preview, head over to Admin Center and create Sandbox (Preview 17.0.16297.0) Creation of Sandbox(Preview 17.0.16297.0) After entering the details of the Sandbox and click on create, there you will get confirmation Dialog. Confirmation Dialog Your Sandbox is now created. Sandbox Created - 17.0.16279.0 (Preview) The Sandbox is now accessible

Business Central v16.5 is out! Update 16.5 for Microsoft Dynamics 365 Business Central 2020 (Application 16.5.15.953 + Platform 16.5.15941) For Release Plan visit   HERE !! For information on the previous release  HERE !! Business Value: 1.Upgradation for Customer: For New Customers, by default, the environments will be from v16.5. For existing Customers, Business Central v16.4 will be automatically upgraded to v16.5. 2. Previous Resolved Issues: ID Title Functional Area 369662 “Failed to acquire an access token" error message when you try to setup any Oauth2 integration. Integration Workaround:  Go to nuget.org and download the required package by clicking "Download package":  https://www.nuget.org/packages/Microsoft.Identity.Client/4.14.0 . Extract the contents. Copy the contents from .\microsoft.identity.client.4.14.0\lib\net45\* to the NST binaries location. Restart the NST. 3. Platform Hotfixes: ID Title 365943 Partner licenses do not grant access for device users.