One of the main reasons for the popularity of microsoft dynamics nav upgrade is its simple to learn interface and its adaptability. Microsoft Dynamics NAV is a famous ERP framework among fair size associations. It’s known for being anything but difficult to introduce and get familiar with its interface. It’s a crucial framework for most retailers as it controls your financials, flexible chain, deals, business insight and that’s only the tip of the iceberg.  As retailers develop however. the requirement for incorporating their NAV ERP gets apparent. Your ERP isn’t the main framework expected to run your activities. Retailers must have similar information between their POS, eCommerce, commercial center, 3PLs, and other significant frameworks. Coordinating Microsoft NAV with other retail frameworks is very difficult. Introduction: No. Series is used to create records in Dynamics NAV with unique numbers. Unique numbers are assigned to data records automatically using No. Series. The format to be used for the No. Series should be set up initially once which consists of a combination of numbers and alphabets. Pre-Requisite: Microsoft Dynamics NAV Purpose: In this article, I will be demonstrating the procedure to create a custom No. Series in a custom table. Procedure: Create a new field in Table 311 – Sales & Receivables Setup which will save the No. Series selected. Navigate to the properties of this field and in TableRelation property select Table 308 which is ‘No. Series’. Add the newly created field ‘CF_CreditNoteEntity’ to the Page 459 – Sales & Receivables Setup so that it is accessible to the user from the NAV windows or web client. Now create a new field ‘No. Series’ in a custom table with Data Type ‘Code’. Navigate to the properties of the No. Series field and in TableRelation property select Table 308 which is ‘No. Series’. Note: ‘No.’ field is the primary key of the custom table which will save the unique No. Series. Create two new variables in C/AL globals in the custom table. a. SalesSetup of DataType ‘Record’ and Subtype ‘Sales & Receivables Setup’ which is Table 311. b. NoSeriesMgt of DataType ‘Codeunit’ and Subtype ‘NoSeriesManagement’ which is Codeunit 396. In OnInsert() trigger of the table add the following code: In OnValidate() trigger of the primary key field which will save the unique No. Series add the following code. In this scenario, I have added it to the OnValidate() trigger of ‘No.’ Go to ‘No. Series’ which is Table 308 and create a new entry for the No. Series to be used. To generate ‘No. Series’ automatically you need to select ‘Default Nos.’ checkbox. If you also want the field to support manual nos. then you should select the checkbox ‘Manual Nos’. The ‘Last No. Used’ field gets updated automatically when a record is created and the unique No. Series is inserted in the table. Navigate to Sales & Receivables Setup which is Page 459 and select the No. Series for the newly created field in step 1 from the drop down list.                                                                                                                   Hence, automatically when you create a new record, the No. Series will get inserted and a unique record will be created. Conclusion: Thus following this procedure, a custom ‘No. Series’ can be created for a custom table with any combination of alphabets and numbers which will create unique records.

Introduction: To upgrade the database to NAV 2017, following steps must be completed. Convert the Database Upgrade the Application code Upgrade the Data For Converting the database, refer this link For Upgradation of the Application code, refer this link  This blog describes the steps to Upgrade the Data. Pre-requisites: A FOB file that contains the upgraded application code and upgrade toolkit. All application objects in the old database have been built. The database schema has been synchronized in the old application. All application objects are unlocked. All Microsoft Dynamics NAV Server instance records have been cleared from the dbo.Server Instance table in the old database in SQL Server. Updated permission sets permissions XML files. Windows Poweshell Sql Server Management Service(SSMS) Steps: The first seven steps are completed in the ‘Converting the database from NAV 2016 to NAV 2017’. SQL Backup Upload 2017 Licence Delete all objects from the old version database i.e NAV 2016 Uninstall NAV 2016 and install NAV 2017 Convert the NAV 2016 Database Connect to the server instance Run the Schema synchronization Importing the application objects: Import the all merged file (.fob) created in the upgrade of the application code. The system will prompt to open worksheet Click on Replace All then click on OK. Now import the upgrade code. This upgrade code is located in the NAV DVD in the Upgrade Toolkit folder NAV DVD > UpgradeToolkit >Data conversion Tool Import the Upgrade9001000.FOB file for upgrade from NAV 2016 to NAV 2017. Here 17 objects are imported. Run the Schema Synchronization: Open the Microsoft Dynamics NAV 2017 Development Environment, navigate to Tools menu then click on Sync. Schema For All Tables > With Validation. This will pop up a dialogue box, click on Yes. If Sync.Schema with validation pops up an errors like below ‘There is already an object named ‘CRONUS International Ltd.-$UPG Item Category’ in the database follow the below steps: Launch SSMS(SQL Server Management Studio), expand the Database converted Select the table and run the query to drop it Run the Data Upgrade Process Open the NAV 2017 Development Environment as Administrator. Navigate to Tools tab > Data Upgrade > Start. This will pop up a dialogue box, click on yes. Select the Execution mode as parallel, enable show progress and click on OK. If there are any errors you may get an error dialogue box. To view the error, Open Windows Powershell as Administrator, enter the below command Get-NAVDataUpgrade serverinstancename -Erroronly Get-NAVDataUpgrade Upgrade -Erroronly The above error is shown in the Codeunit 104075,compile the codeunit. The codeunit will pop up errors which needs to be fixed. Once the error is fixed compile all objects then run the Data upgrade process step no 10 This process will continue until all the errors are fixed. The data upgrade process is completed without any errors. Delete the upgraded objects After the upgrade is completed, delete the upgraded objects imported from the Upgrade Toolkit. Filter the upgrade objects by their version list. Select all the upgrade objects and click on Delete Set the Synchronization schema to Force and click on OK  After Deletion, compile all objects. Import upgraded permission set and permissions. Open the NAV 2017 Development Environment, open the NAV 2017 database ‘Demo Database (10-0). Navigate to XMLport 9171 Import/Export Permission Sets and click on Run Choose Export option and click on OK and save the file. Repeat the same procedure for XMLport 9172 Import/Export Permissions Now open the Upgraded database in NAV 2017, navigate to page 9802 Permission Sets and click on Run. Delete all permission sets except Super permission. Run XMLport 9171 to import permission sets, select the Import option then OK Select the permission sets exported  then click on OK. Run the Page 9802 Permission Sets, all the permission set are imported.  Repeat the same for XMLport 9172, import the permissions. Set the language of the upgraded database. Navigate to Tools select the language required then on OK. Add Control Add-ins Browse in the search bar to Control Add-ins to verify the below control Add-ins are present. Dynamics.Nav.Client.BussinessChart Dynamics.Nav.Client.PageReady Dynamics.Nav.Client.PingPong Dynamics.Nav.Client.VideoPlayer Dynamics.Nav.Client.SocialListener Import Payment Service and Data Encryption Key (optional). If we have used payment service in our old database then we need to re-set up payment service in NAV 2017 by importing the key. Browse to Payment service Connection set up in the search bar Click on Upload Key to upload the encrypted key. This key was downloaded in the previous version using the Download key.  To import key for Data Encryption Management, browse to Data Encryption Management in the search bar. Click on Enable Encryption to enable the encryption and import the key using Import Encryption Key. Before importing the key needs to be exported from NAV 2016. Conclusion : After the Upgradation of the Data, the upgradation of  NAV 2016 to NAV 2017 is successfully completed.  

Since integrating your ERP takes time and resources, you want to make sure the project is worth it before you dive in. There are many common signs that indicate that you need microsoft dynamics nav upgrade . Without integration, retailers rely on manually entering the same data into multiple systems. If you have teams or individuals solely dedicated to spending hours manually moving data, then you’re ready for automation. All these hours moving the data yourself could be better spent, like improving your customer experience. Relying on manual data entry is also more prone to human mistakes. All it takes is a typo in one system to offset your data. Bad data can lead to inconsistent product information across sales channels, inaccurate delivery addresses for online customers, and wrong inventory counts Introduction: Microsoft Dynamics NAV control add-ins can be created using the NAV .dll assembly viz. Microsoft.Dynamics.Framework.UI.Extensibility.dll assembly. This .dll binds the NAV control add-in and the NAV environment. This control add-in has to be implemented in Visual Studio and then registered in Dynamics NAV by navigating to Control Add-ins. Pre-Requisite: Microsoft Dynamics NAV Purpose: In this article, I will be demonstrating the steps to create and use a Client control add-in in Microsoft Dynamics NAV. Procedure: Open Visual Studio. Create a new C# class library project and add a reference to the Dynamics.Framework.UI.Extensibility.dllassembly. This assembly is present in the following directory: C:\Program Files (x86)\Microsoft Dynamics NAV\100\RoleTailored Client. In the Visual Studio project namespace, create a new interface and add code for the control add in. The code is mentioned below:[ControlAddInExport(“NAVaddin”)] The name ‘NAVaddin’ will be used while registering the control add-in in Dynamics NAV. Now you need to sign the assembly. Navigate to properties->Signing->select Sign the assembly. In the Choose a strong name key file drop down list, select ‘New’. In the Key File name enter an appropriate name and clear the ‘Protect my key file with a password’ check box. The next step is to generate a unique public key in Visual Studio for the project as this public key is required while registering the control add-in in Dynamics NAV. Navigate to Tools->External Tools. Parameters to be filled are as below: Title: Get &PublicKey Command: C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\sn.exe Arguments: Get &PublicKey Now, ‘Get PublicKey’ will appear as an option under Tools which on clicking will generate the public key for the project. After clicking ‘Get PublicKey’->the public key is generated and displayed as below: Save and Build the solution. After successful build of the project, the .dll file will be generated.   Creating the Resource .Zip File.You must create a single .zip file containing manifest and any of the resource files used in Visual Studio. This .zip file has to be used while registering the .dll in Dynamics NAV. The next step will be to copy the .dll file to two locations in Dynamics NAV as given below: C:\Program Files\Microsoft Dynamics NAV\100\Service\Add-ins C:\Program Files (x86)\Microsoft Dynamics NAV\100\RoleTailored Client\Add-ins Go to NAV administration and restart NAV services so that the changes are reflected. Navigate to ‘Control Add-ins’ in NAV windows client and create a new Control add-in. Add the same control add-in name which is mentioned is step 2: Click on ‘Import’ action to import the .zip file containing all the Visual studio resources as created in step 7. After performing these steps, the client control add-in will be registered in Dynamics NAV and the triggers defined in Visual Studio, if any will be visible in the NAV Development environment if the Control add-in is selected in the properties of the control. Conclusion: Using this procedure, you can create complex functionalities in Visual Studio and use the .dll control add-in file in Dynamics NAV. I have created SMS functionality from NAV and Digital Signature functionality in NAV using the above procedure of adding a client control add-in.

Introduction: To upgrade the database to NAV 2017,  following main steps must be completed. Convert the database Upgrade the Application code Upgrade the Data This blog gives a steps wise procedure to covert the database from NAV 2016 to NAV 2017 Pre-requisites: Microsoft Dynamics NAV 2016 Microsoft Dynamics NAV 2017 Microsoft SQL Server Management Studio(SSMS) Steps Backup NAV 2016 Database    Open SSMS and connect to the SQL server. Expand the Database to NAV 2016 Database i.e ‘Demo Database (9-0)’. Navigate to Task > Back up. Click on Add then Navigate the path where you want to store the back up(.bak) file by clicking on the Assit edit button. Specify the file name then click on OK. A pop up displays after the back up of NAV 2016 database is taken. Clear all Microsoft Dynamics NAV Server instance records from the dbo.ServerInstance table in the database on SQL Server.You can do this by using SQL Server Management Studio to open and clear the table. Upload 2017 Licence file in NAV 2016 Database ‘Demo Database (9-0)’ Navigate to File > Database > Alter. In the Integration tab, Enable Save licence file and select the licence file of NAV 2017 then click on OK. Alternatively, Select the Tools menu > Licence Information then Upload. Restart the NAV Server Instance in the Microsoft Dynamics NAV admin. Uninstall NAV 2016 and Install NAV 2017. Convert the NAV 2016 Database to NAV 2017. Open Microsoft Dynamics NAV 2017 Development Environment, select the NAV 2016 database i.e ‘Demo Database (9-0) and click on OK. Till will prompt to convert the database dialogue box. Click on OK. A confirmation dialogue box pops up. Click on OK. This will take few minutes. A message pops up once the database is converted. Connect the Server Instance to the converted database Open Microsoft Dynamics NAV Administration, Click on Add Instance. Specify a Server name and unique port numbers then click on OK. An instance is created, open the instance, click on edit, expand the Database tab. In the Database Name specify the converted database name then Restart the instance. In the below screenshot NAV90 is the server instance name for the converted database. Open the converted database in the NAV 2017 Development Environment. Navigate to the Tools menu > Options. Specify the Server Instance name, Server Port and the Management port. Click on OK. Make sure the user login has access to the Converted database. Open SSMS, expand Logins and select the user. Under the ‘Select a page’ tab, Select User Mapping, enable map for the converted database and master database and enable db_owner then click on OK Under master database, expand the Tables, select the Dbo.$ndo$srvproperty then properties. elect the Permissions then select the user and grant Select permission to the user. Restart the Server instance after applying the above permissions. Run the schema synchronization to initialize the database. Open the Microsoft Dynamics NAV 2017 Development Environment, navigate to Tools menu then click on Sync. Schema For All Tables > With Validation. This will pop up a dialogue box, click on Yes. After synchronizations, navigate to Tools menu > Build Server Application Objects. Building the application makes sure that the database is also synchronized in the SQL server and compiled. Building the application may lead to compilation errors which needs to be fixed. Follow the below link to fix .NET variable errors refer this link Build the Application again until the Build is successful. Conclusion: The database is successfully converted to NAV 2017. The next step is Upgrade the Application code for which you can refer this link

Introduction: In this article, I will be explaining the procedure to display amount in words in a report of Microsoft Dynamics NAV. Pre-Requisite: Microsoft Dynamics NAV 2016 Procedure: Step 1: Declare the following variables in C/AL Globals: ‘RepCheck’ is a variable of DataType ‘Report’ and Subtype ‘Check’ which is Report 1401. ‘NoText’ is a variable of DataType ‘Text’ with Dimensions Value as 2 which is set by navigating to the properties of the ‘NoText’ variable. ‘AmountInWords’ is a variable of DataType ‘Text’ which will store the final result of the amount in words. Step 2: Now in my custom purchase order report, I want to display the Amount to Vendor in Words. So in the Purchase Header – OnAfterGetRecord() trigger, I have put the following code: I have declared a variable ‘AmountVendor’ of DataType ‘Decimal’ in which I will be storing the ‘Amount to Vendor’. I have rounded off the Amount to 2 decimal places. AmountVendor:= ROUND(“Purchase Header”.”Amount to Vendor”,0.01); Now add the following code to display the Amount in Words: RepCheck.InitTextVariable; RepCheck.FormatNoText(NoText,AmountVendor,”Purchase Header”.”Currency Code”); AmountInWords:=NoText[1]; So the complete code looks like below: Step 3: Now get the variable ‘AmountInWords’ under the DataSource ‘Purchase Header’ in the report and display it in the design layout of the report. After saving and running the report the Amount to Vendor will be displayed in Words as shown below: Conclusion: Thus using the above procedure and the Report 1401 i.e. ‘Check’ report, the amount in words can be easily displayed in any report of Microsoft Dynamics NAV 2016.  

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.