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

Introduction: After upgrading Business Central to version 17 (Wave2 2020), I found that there was an error telling me that WebService Key is going to be deprecated soon. Web Service Access Key is deprecated. Hence, I decided to explore and probably make it easier through this blog. Pre- requisites : Admin Access to Office 365 Admin Access to Azure Demonstration: 1. App Registration on Azure Portal: To enable OAuth authentication for any apps in Azure Active Directory, you will need to perform App Registration and set up the permissions and security details. i.) Register the App: Search for 'App Registration' on the Azure Portal. Click on New Registration Type in the App Names, Account Types and Redirect URI. Registering Application ii.) Setup API Permissions: Go to API Permissions > Add Permissions > Business Central App > Select Delegated Permissions > Select Other Permissions and Financials > Add Permissions Button. Setup API Permissions iii.) Setup Client Secr

Introduction: In my previous blog on setting up the App Password for Outlook after enabling Multi-Factor Authentication, refer to How to bypass Multi-Factor Authentication This blog is an update on the changes made to the process creation of App Password and is relatively easier to follow. I faced an issue where the ' View Privacy Link ' button was missing in Settings & Privacy > Privacy View Privacy Link Missing - Office 365 / Microsoft 365   Pre- requisites : Microsoft 365 (a.k.a Office 365) Demonstration: In portal.office.com, go to the Users icon on the top right and select ' View Account' View Account Head over to the ' Security Info ' navigation on the left side and click on ' Add Method Adding Method in Security Info You need to select the Method as ' App Password ', provide the ' App Name ' and copy the password generated for further use Adding a Method Adding AppName Copying App Password I tested the copied password in SMTP Ma

Introduction: While going through the Setup of Business Central with Jet Reports as per the article from Jet Global, I noticed that for some reason I wasn't finding the same options as mentioned in the article. Hence, I decided to try somethings on my own, and here are my findings. In this blog, I would like to cover the JetReport Setup with Business Central Sandbox or Production. Pre- requisites : Microsoft Excel Microsoft Dynamics 365 Business Central Jet Report Extension Setup in Business Central Jet Report Add-In installed References: https://support.jetglobal.com/hc/en-us/articles/360010307533-Create-A-Business-Central-Public-Cloud-Web-Services-Data-Source Demonstration: As you know that the setup wasn't exactly as mentioned in the article. 1. Data Source Type: Goto App Settings > Data Source Type > Select WebServices DataSourceType as Web Services 2. Authentication   For Authentication, select the NavUserPassword. Use the Username and Web Service Key from Users. Use

  Introduction: Today, as I was working with Real-Time Integration with TCI Scribe, I noticed that the integrations which were working prior stopped working. Although the URL when triggered through the POSTMAN app it works fine. The error that was received is ' {​​​​​"The underlying connection was closed: An unexpected error occurred on a send."}​​​​​ ' Pre- requisites : Microsoft Dynamics NAV / Business Central Understanding of .NET Interoperability Postman App Test Endpoint for API Procedure: I have used NAVWebRequest or HTTPWebRequest as .NET interoperability in NAV referring to https://dynamics.is/?p=2739   1. Debugging the issue: In order to make sure that the coding is correctly triggering the URL with POST call and JSON Data Payload, I created an endpoint on Request Bin and the solution seems to be working. Request Bin Also, when triggering the URL through Postman, the response is correctly generated. Postman Trigger 2. Finding the issue and possible solution u

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