For Freshers, starting to learn TCI might not know how to create NAV connector. NAV is On-premise and since its On-premise its Agent is need to be installed. So, in this blog you will get to know how to create NAV connector as well how to install the agent on its server. Firstly we will see how to install the Agent on NAV server. For that you need to ON the Virtual Machine from the Azure Portal, here our Virtual Machine’s name is NAV2018 or you can contact IT Admin to do the same for you. After your VM is ON you now need to connect to the RDP. Download the RDP file. Run the downloaded file and Click on Connect. Enter Username and Password and click OK. Now you are connected to NAV 2018 server Now login to https://app.scribesoft.com and from More select Agents. Click on the + button to add agent on NAV server. Click on Install On-Premise Agent Copy the Agent Key for further use. Click on Run Tick the check box and click Next Click Next. Paste the Agent Key which you earlier copied and Click on Next Check the location and click on next. Now click on Install Agent Now your Agent is Installed and you can now create the connector. Click on the + button and add new connector. Now you can fill up the necessary data such as OData URL, User and Password, Company Name which you will get from NAV ( you can check this by searching USERS). Also choose the agent as NAV Agent. Test the Connector and Save the Connector.

Introduction: Work around to solve the error ‘The request for path /NAV2018/dev/apps failed with code 422. Reason: The value “1473493” can’t be evaluated into type Date’. This is a bug accepted by Microsoft. Thus this blog demonstrate the workaround to the bug until it gets fixed. Pre-requisite: NAV 2018 Demonstration: Converting the text files to AL files from C/AL suing TEXT2AL utility, Thus, InitValue property of the field is set as per the C/AL object but, it throws the following error Workaround to this is either comment out the code and validate the field and add the data. Conclusion: This is a bug and the following method is only a quick fix until a new version is released.

Introduction: In NAV 2018, after installing the extension the data of the newly created fields using extension is to be filled. But after upgrading the extension the data of the added field gets flushed out. Thus, this blog demonstrates how to configure to prevent the data from getting flushed. Pre-requisites: NAV 2018 CU2 along with its Installation DVD Zip Demonstration: Goto Visual Studio Code and uninstall the previous version AL Language Extension. Install the extension from AL Language from the path “C:\Users\<Username>\Downloads\CU 02 NAV 2018 NA\NAV.11.0.20348.NA.DVD\ModernDev\program files\Microsoft Dynamics NAV\110\Modern Development Environment/ALLanguage.VSIX” file. Select the .VSIX file. Reload the AL Language Extension. Adding the following lines to ‘launch.json’ file If the data is to be saved :-  “schemaUpdateMode”: “Synchronize” If the data is to be flushed :- “schemaUpdateMode”: “Recreate” Conclusion: This feature wasn’t included NAV 2018 and the data used to get flushed everything the extension was upgraded. Thus, the data flushing issue was resolved in NAV 2018 CU2 version.

Introduction: In previous versions of NAV, employees had to be set up as vendors to post expenses. Now, NAV 2018 allows expenses to be posted against employee cards, with a range of tools to simplify the process. Features: In NAV 2018, in the Account type field a new value of Employee is added. Create Journal entries directly for employees – only supports local currency (LCY) Employee posting group, definable on the employee card. Make payments to the employee in the Payments Journal. Get payment suggestions with a full list of outstanding employee payments. Apply payments to open employee entries in one go, linking the payment to the employee journal entry and closing both. Correct mistakes with unapply payments. Posting a general journal line with Employee as account type or balancing account type will generate an employee ledger entry. When posting a general journal line for an employee, the Document type field must be either blank or set to Payment. Conclusion: This feature is very useful for Reporting purpose as well as to maintain Employee wise details in the system.