Introduction: Many of client required report with dynamics Column in Navision. We all know dynamics data is displaying top to bottom. But what happen if customer want data left to right. And As data increase Column also increase in the report. In this blog, I will show you Item inventory report, where Item will display in row and location will display in Column. But when you add any new location in Navision and Post any Item Journal, sales, purchase  entry for that location, that new location will added in report Column. Steps 1: Open Navision Development Environment. Go to Object Designer.  And Create New Reports. For Demo I created New Report “ Item By Location New “ report ID 50029. Steps 2: GO to Design mode of that report. Take Item table in Data Item and Item Ledger Entry table in 2nd data Item. Relation set DataItemLink “Item No.=FIELD(No.)” in Item Ledger entry Property. Select the Column from the table. For the demo, I have taken only 4 fields, you can as fields as you’re your requirements. Steps 3: Go to view and and select Layout option. Here I am using SSRS Report Builder. Click on Insert , then click on Table button and select Table  Wizard Option. And select 1st option as per screen shots. Step 4: In Column groups click and drag Location code , for Row Group Item No. and in Value Sum of Quantity. Click on next and finish. Steps 5: Now add Item description fields on right side of Item. Step 6: Save the report and run. Click on preview. Steps 7 : Create new location and post Positive adjustment entry for that New location and again preview the report. New location is added in that report and its inventory Update. Conclusion :- With this method you can create dynamics column reports, which can be print left to right column.  

Introduction: This article focuses on how to restrict other users and allow only a particular user to user a specified action button in a Page in NAV 2017. The requirement was such that the page Purchase quote is to be signed off by the CEO and then Purchase order is created. Here, an action button is created called Sign off, where on click of the button, the boolean field called Sign off which is an un-editable field is enabled. Only the CEO should have the access to Sign off the Purchase Quote. The other users should be restricted from signing off the Purchase Quote Pre-requisites: Microsoft Dynamics NAV 2017 Steps: 1. In the NAV Development Environment, create a Boolean field. e.g CEO in the User Setup table. 2. Add this field to the User setup page and enable this field for the CEO user. 3. Create a button Sign off in the purchase quote. Create a new codeunit and subscribe it to the action button Sign off. 4. Create a global variable User Setup in the codeunit and refer the below code. 5. In the Windows client/Web Client, browse to Purchase Quote from the search bar. 6. Edit any Purchase Quote and click on Sign off. Here if the User is not the CEO, in the above image the user is OETIADMIN ,a message is displayed ‘Only the CEO can Sign off this purchase document’ 7. If the User is the authorize user to sign off in this case the CEO then the message is displayed as Purchase Quote is signed off.

Microsoft Dynamics Nav integration is a default integration setup for Dynamics Nav that gives an option to integrate and use Microsoft Dynamics CRM entities with itself. The only thing that needs to be done for the integration is to enable the default integration setup after which you are good to go. After the successful integration, the user is able to integrate accounts, contacts, products, user, transaction currency, Sales Order which are synchronise data of Microsoft Dynamics CRM with the customers, contacts, items, Salesperson, Currency, Sales Order and Unit of measure which are the entities of Microsoft Dynamics Nav. This integration or linking of the records eases the process on many levels giving the customer a hassle free transaction and complex free system Introduction: Single sign-on (SSO) in Dynamics NAV is a process which authenticates a user to access NAV Web client and NAV windows client using Office 365 email login credentials. When a new Office 365 subscription is provisioned, the Azure AD tenant for this subscription has to be created. Pre-Requisites Microsoft Azure Active Directory Module for Windows PowerShell Microsoft Online Services Sign-in Assistant You can download the setup of Microsoft Online Services Sign-in Assistant from here Microsoft Dynamics NAV 2017 Purpose In this article, I will be explaining the procedure to configure Single Sign-on in Dynamics NAV with the Office 365 login credentials of a user using Windows PowerShell. Procedure: Go to Microsoft Dynamics NAV 2017 Administration and in the NAV instance enter the Certificate Thumbprint (the certificate can be either an SSL certificate or a self-signed certificate) Save the changes and restart your NAV instance. Go to mmc.exe and navigate to the certificate that is being used for Single sign-on. In mmc.exe, in Personal certificates section, in ‘Manage private keys’, add ‘NETWORK SERVICE’ as a user name and grant full control permissions to ‘NETWORK SERVICE’ user. In mmc.exe, along with Personal certificates section make sure the certificate is present in trusted root certification, Enterprise trust, Trusted publishers and Trusted people. Navigate to the user for which Single sign-on is being set up in NAV and under Office 365 Authentication enter the Office 365 email of the user.  Now run Microsoft Azure Active Directory Module for Windows PowerShell as administrator. Navigate to the Service folder to find NavAdminTool.ps1  module and run the following command in PowerShell to import the module Import-Module “C:\Program Files\Microsoft Dynamics NAV\100\Service\NavAdminTool.ps1” Navigate to the RoleTailoredClient folder to find ps1 module and run the following command in PowerShell to import the module. Import-Module “C:\Program Files (x86)\Microsoft Dynamics NAV\100\RoleTailored Client\NavModelTools.ps1” To import NAVOffice365Administration Module, navigate to the Microsoft Dynamics NAV DVD and then to NAVOffice365Administration. Run the following command in PowerShell to import NAVOffice365Administration.psm1. Import-Module “C:\Users\iotapadmin\Documents\CU 5 NAV 2017 W1\NAV.10.0.16177.W1.DVD\WindowsPowerShellScripts\NAVOffice365Administration\NAVOffice365Administration.psm1” To configure your Microsoft Dynamics NAV Server for single sign-on, you have to run the cmdlet  Set-NavSingleSignOnWithOffice365 in PowerShell with the following parameter set: Set-NavSingleSignOnWithOffice365 -AuthenticationEmail “YourAuthenticationEmail” -NavServerInstance “YourNAVServerInstance” -NavUser “YourNavUser” -NavWebAddress “YourNavWebClientAddress” -NavServerCertificateThumbprint “YourNAVServerCertificateThumbprint” -NavWebServerInstanceName “YourNavWebServerInstanceName” After entering this command a pop up box shown as below appears with the Office 365 email ID given in the above command and you have to enter the password of the given Office 365 email ID: After entering the password, the below output will appear in PowerShell: Copy and save the URL that appears at the end in PowerShell as it will be required later. Navigate to the ClientUserSettings file of the user and change the following parameters:Change ClientServicesCredentialType parameter value from ‘Windows’ to ‘AccessControlService’. Change the ACSUri parameter value to the value of URL link generated after the PowerShell command runs which I have mentioned in step 8. The parameters of the web client web.config file have not to be modified manually. It is automatically modified after the PowerShell command script runs. After SSO is configured, when you start Dynamics NAV Windows client and Web client, you have to enter the credentials of the Office 365 email ID which is provided while running PowerShell script in step 8. Fig: Windows Client Fig: Web Client

As NAV 2017 introduced new features, they have added some fields in Sales & Receivable Setups. These fields are explained below : Following new fields are added in the Sales & Receivable setup as compared to NAV 2016. Default Item Quantity Create Item from Description Allow Document Deletion Before The functionality of these fields are explained below : Default Item Quantity : By default it will not be checked.  If the user checks it then, the default quantity in a sales line will automatically be set to 1 . (This will work only if the Type in the Sales Line is Item). Create Item from Description:  By default it will not be checked.  If the user checks it then, while entering Item description in Sales Line if the system is unable to find the same description in Item master, the system will prompt the user to create a New item or Select an Item From Existing List, as shown below. 3. Allow Document Deletion Before: If the date is provided in this field, system will allow to delete the document (Invoice & credit memo) only after checking the posting date which should be before the date provided in these field. This features might be very small but are very useful in day to day activities  by the user.

Introduction: Purchase Quotation use to purchase items or services, and want to receive competitive offers from multiple vendors. In Purchase quote, vendors provide the prices and delivery times for the quantities of items that they specify. In the Search box, enter Purchase Quotes, and select the related link. Click on new to create new purchase quote. In the Buy-from Vendor No. field, select the vendor’s number. Select item in the type field in quote line. In the field, select the item number to be ordered. Enter the quantity you want to order in quantity field. Enter the Order date, Due Date, Expected receipt date on Purchase quote header. Once receive the price from vendor enter the price in Direct unit cost field. On Action tab click on Make order to create Purchase order from Purchase quote. You will get below Infolog when purchase order will be created. Conclusion: Purchase quotation is good feature in Dynamics NAV which allow you to create quote for items and services that you want to purchase from several vendors based on prices and time.  

Introduction: In this article, a workflow response is created in the standard purchase order workflow. This response sends an email to the vendor after release of the purchase order i.e when the send approval request of the purchase order is approved by the authorized approver, the status of the purchase order changes to Released  afterwhich an email is sent with  attachment in a .pdf format to the vendor. Pre-requisites 1.Microsoft Dynamics NAV 2017 Steps: 1. Configure smtp mail setup in the front end where you need to enter the sender’s email id and password. 2. Now to create a workflow response we need to create a global function in a new codeunit. Navigate to View tab select C/AL Globals or (Ctrl+G). click on the functions tab and under the Name type the function name, by default the function is a local function. 3. To make it a global function, select the function ‘SendEmailCode’ and click on view tab then click on properties. Set the Local to No, this will make the function global. Now click on the function then click on Locals button placed on the right side. Click on the return value tab and set return type as code and length as 128. This function calls another function ‘SendEmail’ 4. Create another global function with another name in this article I’ve used ‘SendEmail’. Set parameter to the record ‘Purchase Header’ and enable it as a variable. 5. In the below code, we first fetch the vendor email id and set it to a variable VendEmail. We use the FileManagement codeunit and set the ServerTempFileName as a ‘pdf’ file. We then save the report as pdf file.  We then use SMTPMail codeunit, The SMTPMAIL.CreateMessage sets the sender’s email id and recepients email id, subject of the email  SMTP.AddAttachment function attaches the purchase order in  a .pdf format. In SMTPMail.AppendBody function we can specify the body of the email. SMTP.Send functions sends the email. 6. Now the response created of sending email to the vendors need to be added to the workflow response library.  Create a global function, in the properties of the function click on the event field and select subscriber. In the Event Publisher object select the Workflow Response Handling codeunit (codeunit no. 1521)  In the Event Function field select OnAddworkflowResponseToLibrary.  Select the function and click on the Locals button and in the variables tab, create a variable for codeunit Workflow Response Handling. In the below code, we add the response to workflow library with name SendEmailVendor. This name is a text constant 7. Now to execute the response we need to create a global function. Create a global function, in the properties of the function click on the event field and select subscriber. In the Event Publisher object select the Workflow Response Handling codeunit (codeunit no. 1521) In the Event Function field select OnExecuteWorkflowResponse.  In the Locals for this function, in the variable tab create a variable for the record ‘workflow response’. 8. In the Dynamics NAV front end , navigate to workflows from the search bar. In the purchase order approval workflow, add the response ‘Send Email To Vendor’ then enable the workflow. 9. Navigate to Purchase order from the search bar and click on Send approval request button on the menu bar. 10. The email is sent to the vendor.  

Introduction: In my previous blog, I had mentioned the steps required to setup ACH payments to vendors in NAV. For more details of my previous blog, click here. After all the setups are done, the next step will be to Export and Transmit the ACH payment file. In this blog, I will be giving the procedure for the same. Pre-requisite: Microsoft Dynamics NAV 2017 (North America NA version). Procedure: Step 1: Navigate to Payment Journal. I have created a new payment general journal batch named ‘ACH’. Step 2: Select ‘Suggest Vendor Payments’ which processes open vendor ledger entries and creates a payment suggestion as lines in the Payment Journal window. Enter the Last Payment Date and the Posting Date. Enable Find Payment Discounts, Summarize per Vendor to create one line per vendor for each currency in which the vendor has ledger entries. Select the Bal. Account Type as ‘Bank Account’ and select the bank from which ACH payment has to be made in Bal. Account No. Select the Bank payment type as ‘Electronic Payment’. Select a filter as payment method code is ‘ACH’ so that open vendor ledger entries with vendor payment method code as ACH are displayed. Step 3: Export payments on journal lines to a file prior to transmitting the file to the bank. Select the ‘Export’ action. Output method is basically for the Remittance advice. Select the output method to save it. Step 4: The export file will be created automatically and saved in the Export folder. Now logon to the bank, upload the file and once verification is given from the bank that everything is perfect then it can be transmitted. Step 5: To transmit the payment, click on transmit. After transmitting the payment, NAV will remove the notepad file from export folder and transfer it in the transmit folder. Step 6: Last step is to post the payment. Note: To edit the format of the export file as per the bank requirement, you need to edit format of the Codeunit 10090 – Export Payments (ACH). Using the above procedure, it is possible to do ACH payments to vendors in Microsoft Dynamics NAV.  

Introduction: Transfer order are mainly used for Transfer of inventory from one location to another location. Below are the steps to create transfer Order In the Search box, enter Transfer Orders, and select the link Click on New button to create new transfer order. Select the Location in Transfer from Code field from where you want to ship the Inventory Select the Location in Transfer to Code field from where you want receive the Inventory. Select the Location in In-Transit Code field which is used for mainly material is shipped from one location but not received in another location. Select the Item, quantity on Transfer order lines. On Action tab, click on post button to ship the Inventory from one location. Select ship in message Box and click on OK. You can checked Quantity which are shipped in Quantity Shipped field. Then again click on Post button to receive the inventory in another location. Select Recive in message box and click on OK. You can checked Quantity which are received in Quantity Received field. Conclusion: Transfer orders involve posting items as shipped from one location and posting them as received at the other location.

Dynamics NAV 2017 gives the possibility to define own product attributes (e.g. colour or size) and assign them to the corresponding item, so the user can refine and structure his article range much better. Till NAV 2016 Item Categories were a simple List Where we can specify the Categories and some other default parameters but in NAV 2017 user can specify attributes in the Item categories. 1. In the Global Search, search for Item Categories. 2. User can define attributes in Item categories. 3. An Attribute assigned to the Parent will automatically get assigned to the Child Item Categories. Item categories also ensure a better hierarchical structuring of the items. While the previous version of the ERP system only offered one main and one hierarchical level, the Dynamics NAV 2017 version will enable multiple hierarchy levels to be added to the main hierarchy level, which can be defined specifically and in multiple languages. Items can be accordingly allocated to the respective categories. This feature ensures consistency across related items, saving considerable amounts of time during allocation.

One of the most dynamic and popular ERP systems among mid-sized organisations is microsoft dynamics nav integration. This is popular for its easy installation and super easy and understandable interface which literally anybody could learn within no time. It is the most needed system for the retailers where it controls your financials, supply chain, business intelligence and much more.  As retailers grow though. the need for integrating their NAV ERP becomes evident. Your ERP isn’t the only system needed to run your operations. Retailers must share the same data between their POS, eCommerce, marketplace, 3PLs, and other important systems. Integrating Microsoft NAV with other retail systems is no small task. To get you started, we put together this beginner’s guide so you can learn all the basics when considering integration. Introduction: Automated Clearing House (ACH) payments to vendors can be done through Microsoft Dynamics NAV. To do ACH payments, setup is required to be performed basically in four areas: Company information, Bank Account card, Vendor card and Vendor bank account. Pre-requisite: Microsoft Dynamics NAV 2017 (North America NA version) Purpose: In this blog, I will be covering the setups required to perform ACH payments to vendor bank accounts in NAV. Procedure: Step 1: Navigate to Company information card and enter Federal ID No. Step 2: Navigate to Bank Accounts and select the bank from which payment will be done to the vendor. Enter following fields in the bank account card 1. Bank Branch Number 2. Bank Account Number 3. Last Remittance Advice No. 4. Export format: Select from given three options i.e. US, CA (Canada), MX (Mexico) 5. E-pay Export File Path: Enter the path where you want the export file to be saved which will be transmitted to the bank. End the file path name with ‘\’ 6. Last E-Pay Export File Name: Enter a name of the file with numeric value as the last digit to the right and the extension. The first file name which will be saved will be incremented by 1. 7. E-Pay Trans. Program Path: Enter the path of the transmit folder. When user selects transmit in payment journal, NAV moves the file formed in Export folder to Transmit folder. End the file path name with ‘\’ 8. Transit No.: Enter the Transit number of the bank which is the bank’s routing number. Step 3: Navigate to the Vendor card and perform the following steps. I have created a new payment method code i.e ‘ACH’ so that it is easy to differentiate vendors that use ACH as their method of payment from vendors that accept checks. Select ‘ACH’ as the payment method code. Now, navigate to the Vendor’s bank account. Enter following fields in vendor’s bank account. 1.  Vendor’s bank branch no. 2.  Vendor’s bank account no. 3.  Vendor’s bank transit no. Select the ‘Use for Electronic Payments’ checkbox to enable ACH payments for this vendor. After filling in these fields, select the preferred bank account code in the vendor card. The above mentioned steps are the setups required to perform ACH payments to vendors in NAV. I will be covering the procedure required to export and transmit the payment file which is generated while doing ACH payment to vendors in my next blog.