Introduction: A Single Sign-on (SSO) user experience is achieved between Microsoft Dynamics NAV and the Office 365 Web Applications where the User is authenticated using Office 356 credentials to access NAV Windows client and Webclient. Error: After configuration of SSO in NAV, the Windows client configures SSO successfully but the Web client throws an error. AADSTS50011: The reply address http://localhost/DynamicsNAV100/WebClient/SignIn.aspx?ReturnUrl=%2fDynamicsNAV100%2fWebClient%2f does not match the reply addresses configured for the application: http://localhost/DynamicsNAV100/WebClient/.  Pre-requisites: Microsoft Dynamics NAV 2017 Internet Information Services(IIS) Resolution of the Error: Browse to Internet Information Service(IIS) Select on Microsoft Dynamics NAV, then click on Bindings Click on Add. In the Type Field select ‘https’. In the SLL certificate, select the self-signed certificate generated from the drop down. Click on Restart. Click on Browse link of the Web server Instance and save the url. Configure SSO for Dynamics NAV and in the below command Set-NavSingleSignOnWithOffice365 -AuthenticationEmail “YourAuthenticationEmail” -NavServerInstance “YourNAVServerInstance” -NavUser “YourNavUser” -NavWebAddress “YourNavWebClientAddress” -NavServerCertificateThumbprint “YourNAVServerCertificateThumbprint” -NavWebServerInstanceName “YourNavWebServerInstanceName copy the url saved in the “YourNavWebClientAddress” address. After Binding, Enter your Office 365 credentials and sign in. SSO works successfully for Web client after Binding of the SLL certificate.  

Whether you are a small sized business, a mid-sized one or a large business, Microsoft dynamics nav upgrade is all you must do to gain new heights in your business. Elements NAV clients are passing up the genuine advantages of moving up to Dynamics NAV in the present cloud-based condition. Microsoft is persistently seeing approaches to ad lib the Enterprise Resource Planning Systems or ERPs.  In the event that you overhaul Dynamics NAV, you will be exploiting improved usefulness, new highlights, and upgraded abilities, you can help efficiency, diminish costs, and improve client assistance. Utilizing Microsoft Dynamics NAV Inventory Management, organizations can do errands, for example, setting up elective merchants, mind stock gathering the executives, and get the necessary investigation report easily. Introduction: To track changes that are made to records in a particular table and to store them sequentially in NAV, logs have to be created. Using logs we can record changes that are made to standard or custom fields in a table. In this article, I will be demonstrating the steps required to setup logs in NAV. Pre-Requisite: Microsoft Dynamics NAV 2017 Procedure: 1. Navigate to ‘Change Log Setup’ Page using the NAV windows or web client. 2. In the actions tab, choose ‘Tables’ under Setup group to select the tables and the fields on which changes are required to be logged. 3. A list of all the standard and custom tables will be displayed. Logs can be created on three events: Initially when the record is created, log will be created with the initial value of the selected field to be logged. When the record is modified, log will be created in the system with the old and new value of the selected field to be logged. When the record in deleted, log will be created in the system. 4. You can either select some fields to be logged or select the All fields option. If you select ‘some fields’, click on the ellipses (…) to select the fields on which log will be created. If ‘All fields’ has been selected, by default all the table fields changes will be logged. 5. I have created a log entry on ‘Item’ table on two fields ‘No.’ and ‘Car status’. Car status is a custom field with option datatype. 6. On clicking the ellipses (…) when ‘Some Fields’ is selected, the table field list will be displayed. Select the event when a log record has to be created i.e. Log Insertion, Log Modification or Log Deletion. 7. Now on the Change log setup page, select the ‘Change Log Activated’ checkbox. 8. After creating a record in ‘Item’ table and modifying the values of the ‘Car status’ field, the following logs are created in the system. Date and Time when the log is created is stored which will be useful to get history of events performed in the system at any point. The user ID who is creating and modifying records will be stored. Table caption stores the table name which is selected. Primary Key Field 1 Value stores the Item No. i.e. the unique field in the table. Type of change will be stored i.e. Insertion, Modification or Deletion. For option fields, the old value and new value is stored. Conclusion: These are the steps required to create logs in NAV which will track changes made to the fields selected in the change log setup.

Dynamics 365 for finance and operations is the ultimate solution for all the modern-day organisations facing issues on ERP level and this is the reason it is the most trusted software in the world which all modern-day organisations have adapted. Get a live perspective on the entirety of your numbers and information investigation from Microsoft elements for money related administrations. This cloud-based Microsoft ERP framework gives the important data you have to convey vital, information-driven bits of knowledge to key divisions. Mechanize your stockroom procedures to lessen operational expenses. With Microsoft ERP, your distribution center supervisors can all the more likely control their set aside, quality-control, and picking activities. Furthermore, with an adaptable work process motor, they can quickly react to changing business needs. Introduction This article describes how to deploy Microsoft Dynamics NAV database to Microsoft Azure SQL Database. To deploy a Microsoft Dynamics NAV database to Azure SQL Database, the database must be exported as a data-tier application (DAC) file, which is known as a .bacpac file. This can be performed by using the SQL Server Manager. Pre-requisite Microsoft Azure subscription and access to the Azure Management portal Microsoft Dynamics NAV database is installed on a SQL Server Database Engine instance. SQL Server Manager is also installed on the same computer. Access to the Microsoft Dynamics NAV installation media (DVD). Purpose: The purpose of this article is to deploy NAV Database on Azure SQL database and to access the deployed Database from Microsoft Dynamics NAV Development Environment. Steps: 1. Create and configure an SQL Database Server in Azure a. Create a SQL database in Azure. Click the New button found on the upper left-hand corner of the Azure portal. Select Databases from the New page, and select SQL Database from the Databases page Enter the Database name, resource group, select source Under Server, click Configure required settingsand click on Create a new server. Fill in the details Server name – valid server name Server admin name, password, Location. Here location is the location name where the Virtual Machine is stored When completed the form click on Select. Click Pricing tier to specify the service tier and performance level for your new database. Use the slider to select 20 DTUs and 250 GB of storage. For more information on DTU see what-is-a-dtu After selected the amount of DTUs, click Apply. Click Createto provision the database. On the toolbar, click Notifications to monitor the deployment process b. Create a server level firewall rule The SQL Database service creates a firewall at the server-level that prevents external applications and tools from connecting to the server or any databases on the server unless a firewall rule is created to open the firewall for specific IP addresses. To set a server-level firewall rule, click on SQL Database > Overview page > click Set server firewall on the toolbar as shown in the following image: The Firewall settings page for the SQL Database server opens. Click Add client IP on the toolbar to add the IP address of the computer that is currently being used and then click Save. A server-level firewall rule is created for the current IP address. Make a note of the SQL Database server name because it will be required later. 2. Deploy the existing Microsoft Dynamics NAV Database to an Azure SQL database. Deploy a databse to SQL Azure wizard is used to deploy database between an instance of the Database Engine and an Azure SQL Database server. The wizard uses a Data-tier Application (DAC) BACPAC archive file to deploy both the data and the definitions of database objects. Limitation and Restriction: The Deploy Database wizard supports deploying a database: From an instance of the Database Engine to Azure SQL Database. From Azure SQL Database to an instance of the Database Engine. Between two Azure SQL Database servers. The wizard does not support deploying databases between two instances of the Database Engine. Using the Deploy Database wizard: In the VM, open SQL Server Management studio(SSMS). Click on File > Connect Object Explorer. Connect to the location of the database you want to deploy. You can specify either an instance of Database Engine or a Azure SQL Database server. In Object Explorer, expand the node for the instance that has the database. Expand the Database Before deployment, remove the windows authenticated users as these will cause failure of the transfer process. To remove the windows login user, navigate to Security under the Database in NAV > Users >Click on the Windows user then delete. Right click the database you want to deploy, select Tasks, and then select Deploy Database to Microsoft Azure SQL Database. This opens the Introduction page, click on Next. In the Deployment settings page, click on connect and specify a path to store the .bacpac file in the Temporary file name. Specify the Azure SQL Server name, authentication is SQL Server authentication and enter the login name and password for the server and click on connect. Specify the Edition of Microsoft Azure SQL Database, Maximum database size and service objective then click on Next. This information can be viewed in the Overview of the Azure SQL Database. The progress of the deployment can be viewed in the summary tab. This may take few minutes. The Result is displayed after completion of the deployment of NAV Database to Azure SQL Database. The Database deployed can be viewed in Azure SQL database. Below is the figure showing the deployed database ‘Demo Database (10-0)’ from NAV to Azure. 3. Set up endpoints for the Microsoft Dynamics NAV client services. To add the endpoint you need to follow the below steps, Click on the Virtual Machine( VM) > overview > Resource Group . This will open an overview for the resource group. select NetSecurity (Network Security Group)  then click on  Inbound Security Rules. 4. Configure a Microsoft Dynamics NAV Server instance on the virtual machine. To configure SQL Server authentication: Set up an Encryption key Configure SQL Authentication on Database Configure SQL Server authentication on Microsoft NAV Sever Instance (Non-Multitenant) or Configure SQL Server authentication on Microsoft NAV Sever Instance (Multitenant Deployment) Follow the below steps to set up an encryption key and configure SQL Authentication on … Continue reading Deploy a Microsoft Dynamics NAV Database to Azure SQL Database →

Introduction: With Microsoft Dynamics NAV 2017, we can increase or decrease the inventory of an item from the item card itself. Steps: 1. Navigate to Item card. 2. Select assist Edit next to Inventory and enter the New Inventory. 3. If New Inventory is less than current inventory a Negative Adjustment will be passed behind the scene. 4. If New Inventory is greater than current inventory a positive Adjustment will be passed behind the scene. 5. As soon as we enter new Inventory and click ok. 6. System Looks for an Item Journal template, Create a New Batch for the Item Journal. 7. Insert a New Item Journal Line with Default Location as Blank. 8.Post the Transaction. Important points to remember: 1. All the Transaction posted with this will always post with Blank Location Code. 2. The process will not work if item is Mandatory Serial / Lot Tracked. 3. Unit of Measure will be picked from Item Base Unit of Measure.

Introduction: This blog focuses on displaying the captions of all action buttons of NAV Pages in Arabic language. The requirement was such that the user wanted to view Microsoft Dynamics NAV in Arabic. To suffice this, we installed Arabic module for Microsoft Dynamics NAV 2017 RTC, Server and web client. After installation, only the standard functions e.g New are converted into Arabic language. other functions, buttons are viewed in English. Hence, we need to change the caption labels of these buttons, text constants in Arabic. Pre-requisites: Microsoft Dynamics NAV 2017 Steps: 1. Install Arabic Module for Microsoft Dynamics NAV 2017 RTC, Server, Web Client. 2. Select the objects then Tools > Translate > Export. 3. Change the language code of English i.e 1033 to Arabic 1025. Get translation of English text into Arabic. 4. Save the text file in UTF-8 Encoding. 5. Copy the text file to C:\Program Files\Microsoft Dynamics NAV\100\Service\Translations And C:\Program Files\Microsoft Dynamics NAV\100\Service\Instances then Restart your service Conclusion: After restarting Dynamics NAV services, all the captions buttons of the Pages  appear in Arabic language.

Introduction: In reports, we always a requirement to display header rows of the table on every page. In this article, I will be explaining the steps to do the same in Dynamics NAV. Pre-Requisite: 1. Microsoft Dynamics NAV 2. Visual Studio Report design Environment Procedure: 1. Under layout of your report, click on the arrow under Column groups and then click on Advanced Mode. 2. Now click on (Static) under Row Groups section. 3. Navigate to the properties window of the (Static) under row groups which is displayed on the right. If it is not present, you can open it by navigating to View->Properties Windows or using ‘F4’ button. The properties window will then appear on the right. 4. Now, you need to modify the following properties. Set ‘FixedDate’ property to ‘True’. Set ‘KeepWithGroup’ property to ‘After’. Set ‘RepeatOnNewPage’ property to ‘True’. Using the above steps, your table header rows will be displayed on every page of your report. In the above screenshot, my table header row which includes the captions for the column i.e. row containing ‘No’ and ‘Name’ will be displayed on every page of the report.  

If you have a small or a mid-sized business and still running an older version, you must seriously think of Microsoft dynamics nav upgrade. Microsoft is consistently seeing approaches to ad lib the Enterprise Resource Planning Systems or ERPs. Utilizing Microsoft Dynamics NAV Inventory Management, organizations can do undertakings, for example, setting up elective sellers, beware of stock gathering the board, and get the necessary examination report effortlessly.  70 percent of Microsoft Dynamics NAV clients around the globe keep on running old variants of NAV. Albeit past NAV forms have conveyed ground-breaking operational advantages all through its use, moving up to the most recent adaptation takes execution, spryness and interoperability to unheard of levels. One of the prime explanations behind not overhauling is the hesitance.  Introduction: We often have a requirement to dynamically hide or show fields on a page according to a certain condition. Setting visibility properties of the fields to ‘True’ or ‘False’ do not help as they do not work dynamically. They are only set when the page is opened initially. In this article, I will be demonstrating the procedure to show or hide fields dynamically on a page according to a specific condition. Pre-Requisite: Microsoft Dynamics NAV 2017 Procedure: This is the scenario that I was customizing. I was working on two types of contracts i.e. Rental and Lease contracts. The user has to select the contract type on the page. Now if the user selects ‘Rental Contract’ as the Contract Type then a certain set of fields should be visible to the user else, they should be hidden. The first step is to put all the fields that should be shown or hidden dynamically in a separate group on the page. In the above screenshot, I have put all the fields that should be shown or hidden dynamically when ‘Rental Contract’ is selected in ‘Contract Type’ field which is an option field consisting of OptionString ‘Rental Contract and Lease Contracts for Uber and Non-Uber drivers’ under ‘Rental details’ group. Next, go to the properties of the group that contains the fields which should be dynamically hidden or shown i.e. properties of ‘Rental details’ group. Now in the visible property section, define the condition that triggers the fields to be dynamically shown or hidden. So, I have set the condition that when ‘Contract Type’ equals ‘Rental Contract’ then only ‘Rental details’ group should be visible i.e. I have written the condition as below:  “Contract Type”=”Contract Type”::”Rental Contract” Below are the screenshots of my page: The above shows the three options available for contract type. So if Contract type ‘Lease contract for Non-Uber drivers’ or ‘Lease contract for Uber drivers’ is selected then the ‘Rental details’ group along the fields it contains are hidden. The above screenshot shows that only if ‘Rental Contract’ is selected as ‘Contract Type’, only then the Rental details group and the fields it contains becomes visible.

Introduction: In this article, we will see how to resolve the below error while creating/quering records from NAV. Error Details: Error in calling Operation Query (Lookup Block): Operation failed. Label: Lookup CFSCar, Name: CFSCarLookup, Message: The following error has occurred in the Dynamics NAV Connector: Error: NotFound status code = 404. Resource not found for the segment ‘CFSCar’. Scenario: We have a scenario where we are building Integration Process between Microsoft Dynamics 365 (CRM) and NAV 2017. For NAV entities to be visible in Scribe Online, we have to create a Web Service in NAV for that entity. For more Information, you can check our blog article here. So, we had created a Web Service for Item entity i.e. here Items are Car details so the name ‘CFSCar’ in NAV. The ‘CFSCar’ Entity was visible in Scribe Online. But, recently we were getting “Resource not found” error for ‘CFSCar’ entity. So, we Reset the metadata for NAV connection in Scribe and the entity ‘CFSCar’ was not visible anymore. Troubleshooting: We checked the OData URL for entity ‘CFSCar’. We were getting the below error. Reading the above error, we couldn’t pin point the exact error, so we checked the SOAP Url as well. In the SOAP URL for ‘CFSCar’ entity, proper error was displayed. Error details: Naming Conflict within the “Car Status” object. Fields “Rental/Ops Hold” and Rental / Ops Hold” are both transferred to “Rental_Ops_Hold”. Please find new a name for one of those fields! Turns out there was two Status of same name which was causing an issue. Solution: Once we deleted the duplicate status the error was resolved.

Introduction In this article, the selected record details by the user are exported to excel using Excel Buffer. The requirement was such that Purchase Request is sent to the Vendors to enter the Unit cost of each Purchase Items. These details are sent to the vendors in an excel sheet. After the Unit cost is entered the excel sheet is imported again in the Dynamics NAV. Pre-requisites: Microsoft Dynamics NAV 2017 Steps: 1.Create a report and Data link between the records. 2. Below is the screenshot of the Data Item Link 3. In the globals (Ctrl+G), define the excel buffer table (no 370) to create excel sheet 4. Define the function MakeExcelDataHeader to create the header of the excel sheet and MakeExcelDataBody for the Body Lines. 5. Create a Boolean variable Print to Excel and insert it in the request page. If true then call the function CreateExcelBook. 6. On the PreDataItem Call the function MakeDataExcelHeader and OnAfterGetRecords call the function MakeDataBody 7. Using Excel Buffer table code as below in the functions 8. In the Page, create an action button to run the report. 9. In the page, select the record and click on the Export to Excel button 10. Click on OK 11. This call the report and fetches the data records in an excel sheet. This sheet is then sent to the vendor to enter the unit cost of the respective item. Conclusion: Thus using excel buffer record we can export records from Microsoft Dynamics NAV to Excel sheets.  

One of the most popular and widely accepted ERP systems which is popular in both small and big businesses is the Microsoft dynamics nav integration. The reason for its popularity and wide acceptance is its user-friendly interface and simple installation process. Dynamics NAV customers are missing out on the real benefits of upgrading to Dynamics NAV in today’s cloud-based environment. If you upgrade Dynamics NAV, you will be taking advantage of improved functionality, new features, and enhanced capabilities, you can boost productivity, reduce costs, and improve customer service. Microsoft is continually looking at ways to improvise the Enterprise Resource Planning Systems. Using Microsoft Dynamics NAV Inventory Management, companies can do tasks such as setting up alternative vendors, check on inventory assembly management, and get the required analysis report with ease. Introduction: The item charge functionality in Dynamics NAV gives you the option to include additional costs such as freight, insurance, fuel charges, etc. in the unit cost or unit price of an item transaction. Item charges setup is part of the general Finance setup. Companies can set up different item charge numbers to distinguish types of charges and improve cost and sales statistics. Set up: Path : Financial Management > Inventory > Setup Or Enter “item charges” in the Search box, and then select the related link. Item charge must have a general product posting group and a VAT product posting group. This combination of posting groups determines the general ledger account to which the item charge is posted. Once Item charges has been setup then you can select it on purchase ad sales document line Conclusion : Item charges are an ideal way to record item-related financial transactions without affecting inventory quantities. A company can use item charges in the purchase and sales processes to improve the accuracy of cost and sales information, and contribute to improved decision making.