Do you feel like the vast majority of your information lives in Excel spreadsheets? Joining deals with that, as well, Microsoft dynamics nav upgrade improves your operational productivity so you have all the more convenient information. This permits you to know things quicker like when to move stock from area to another, when to markdown items, and how to showcase in one district versus another. Coordination prompts snappier dynamics.  The present clients request a great deal from vendors. Having the option to settle on basic business choices at the ideal time depends on having perceivability into your tasks. Mix is regularly the way in to that kind of perceivability. It gives you a focal area to oversee and see all your information. Introduction: In this blog, we’ll see the ‘UserName’ authentication in Dynamics NAV. It is used when we want to use the existing Windows User and has a password associated with it. This method is preferred when two or more users use the same machine and require a simple password security so that only they can access their account. Prerequisite: Microsoft Dynamics NAV Procedure: Create a User in Windows Client by going to Administration > IT Administration > General or by typing Users in Search. Create a NAV Server Instance from Administration with Credential Type as ‘UserName’. Change the ClientUserSettings ‘C:\Users\<Username>\AppData\Roaming\Microsoft\Microsoft Dynamics NAV\100\ClientUserSettings ‘Give the Server, ClientServicesPort, Server Instance & ClientServicesCredentialType. Open the Windows Client and enter the credentials. Windows Client HomePage: Conclusion: Thus, this method is preferred when two or more users use the same machine and require a simple password security so that only they can access their account.

Incorporating your Microsoft dynamics nav upgrade isn’t something you do in only a day or two. It takes a cautious arrangement and the correct assets. At the point when done quickly or without appropriate exploration, retailers can be left with expensive tasks that last months and never appear to work accurately. That is the reason a few dealers frequently dread incorporation.  Notwithstanding, these feelings of trepidation shouldn’t prevent you from capitalizing on your retail frameworks. You simply need to accomplish some work forthright and pick the best mix answer for your business. Merchants with in-house IT groups of NAV will here and there decide to assemble their joining themselves.. This requires your group to have top to bottom information on the specialized foundation of NAV and some other frameworks you need to incorporate.  Introduction: Generally, when we set up Microsoft Dynamics NAV, the authentication method by default is ‘Windows’. Windows Authentication : This method allows you to connect to NAV as the current Windows user. Username Authentication : This method requires that the user provide a User name, Password, and Domain name. Users are authenticated using their Windows account NavUserPassword Authentication : Users are authenticated using their Username and password instead of windows authentication AccessControlService Authentication : Users are authenticated using Access control Service. The Username and web service key must be specified. This blog provides a step wise procedure to  authenticate Dynamics NAV using NavUserPassword Pre-requisites: Microsoft Dynamics NAV 2017 Steps: 1. Create a self-signed certificate or use a SSL certificate. To create a self-signed certificate follow the below steps: Download Self-signed certificate generator (PowerShell) from Technet. Open Windows Powershell ISE as administrator. Go to the directory where you saved the New-SelfSignedCertificateEx.ps1 file. Run the following command: Import-Module .\New-SelfSignedCertificateEx.ps1. New-SelfSignedCertificateEx –Subject “CN=<your site name>” –IsCA $true –Exportable –StoreLocation LocalMachine Here <your site name> is the name of your computer. Save the thumbprint generated in a notepad for future reference. 2. Manage the certificate Open the mmc.exe from  Start Go to the File menu, and then choose Add/Remove Snap-in. Select Certificates and choose Add Select the computer account. Choose Finish and then OK. The Expiration Date of the certificate will be 1Y-2D (01 Year – 02 Days) valid From 1 Day Before you create Certificate. 3. Add Permissions to certificate Right Click Certificate. From All Tasks Select Manage Private Keys. Add NETWORK SERVICE permission to the certificate 4. Copy the Certificate Copy the Certificate from Personal / Certificate Node. Paste the certificate into the Trusted Root Certification Authorities/Certificates folder, Enterprise trust, Trusted publishers and Trusted people. 5. Enter the Certificate Thumbprint Open the Microsoft Dynamics NAV 2017 Administration. Click on the NAV instance and enter the Certificate Thumbprint. 6.  Configure IIS(Internet Information Service) Open IIS and click on Microsoft Dynamics NAV 2017 under Sites folder Click on Bindings Click on Add, select https under type and select the certificate under the SSL certificate 7. Create a User in NAV Navigate to CRONUS International Ltd./Departments/Administration/IT Administration/General/Users and create a new user.e.g Username : CHRIS_USERPASS and click on Password and set an appropriate password with a combination of  one uppercase alphabet, one number and special character Set Permission to SUPER under User Permission Set tab. Navigate to the ClientUserSettings file of the user and make the following changes. Change ClientServicesCredentialType parameter value from ‘Windows’ to ‘NavUserPassword’. If you are creating a new server instance mention the Client service port and Server Instance Name. In the web config file(C:\inetpub\wwwroot\<webclientname>) change the  “ClientServicesCredentialType” value=”NavUserPassword”  also change the ClientServicePort and Server instance if you are configuring the ‘NavUserPassword’ for a new server instance 8. Launch Windows Client This will prompt for username and password after which Windows client will launch successfully. 9. Launch Web Client Conclusion: To summarize the blog, create a self signed certificate, assign it permissions and copy the certificate to the necessary folder. Copy the thumbprint in the NAV instance and bind the certificate in IIS. create a user with password and make necessary changes in the ClientUserSettings and web config file.

Introduction: In this article I will be giving the procedure required to hide whitespace if the textbox value is empty and hence not displayed in a report of Dynamics NAV. Pre-Requisite: Microsoft Dynamics NAV Procedure: 1. I have created a simple report with four field values from Customer table for demonstration. 2. I want to display these four fields in a report. So I have created a textbox in the report with these four field values. Instead of creating four different textboxes, I prefer only adding one textbox and giving a line break between each field. 3. The value of the expression of the textbox is as follows: =First(Fields!Name_Customer.Value, “DataSet_Result”) & “<br/>” & First(Fields!Address_Customer.Value, “DataSet_Result”) & IIf(First(Fields!Address2_Customer.Value, “DataSet_Result”)<>””,”<br/>”,””) & First(Fields!Address2_Customer.Value, “DataSet_Result”) & “<br/>” & First(Fields!City_Customer.Value, “DataSet_Result”)  Expression A I’ll explain the Expression A below in detail:  a. “<br/>” is added to insert a line break between each field value. But this expression is used in HTML. So we need to set the textbox to Interpret HTML tags as styles. Hence, you need to double click on your textbox expression. On double clicking the expression, a window opens up which is the Placeholder Properties window. In the Placeholder properties window, set the ‘Markup type’ to ‘HTML-Interpret HTML tags as styles’. b. Now, there is a possibility that ‘Address 2’ field value of the Customer can be empty at times. So a whitespace will be displayed in the report. So to remove the whitespace, I have put the below expression in Point no.: 3 IIf(First(Fields!Address2_Customer.Value, “DataSet_Result”)<>””,”<br/>”,””)  This means that if the Address 2 of the Customer has a value there will be a line break and if no value is present nothing will be displayed and there will be no line break too. Hence whitespace will not be visible in the report. This can be done for any field value which has a possibility to be empty. The output of the report looks like below: I executed the report for Customer No: 01445544-Progressive Home Furnishings If the Address 2 field value is empty:  Report preview is as below:  If the Address 2 has a value present: Report preview is as below: This is the simplest way to hide whitespace in a report if the textbox value is empty.

Introduction: What is Workflow User group? Workflow user group is a group of users under one group title in Workflows with the users’ number in a process sequence such as an approver chain. To define an approval request to be not approved until multiple approvers in a approval chain have approved it, set up approvers with incremental sequence number.Here the approval request is sent to the user with highest sequence number i.e. 1. This user will have to approve the request then an approval will be sent to the next user with sequence number 2 and so on. To define approval request is not approved until multiple equal approvers have approved it regardless of the hierarchy assign same sequence number to the users.Here the approval request is sent to all users in the group at the same time. Here, both the approval requester and approver must be set up in the Approval User Setup. This blog provides a step wise procedure how to create approval workflow using workflow user group. Pre-requisites: Microsoft Dynamics NAV 2017 Steps: I’ll explain workflow user group using a scenario. Scenario:  A sales department has a group of two sales managers. An approval request must be sent to the sales managers if the sales order amount is greater than 4000 and even if one of the sales manager approves the request, the document should be released. 1. Create a workflow user group Navigate to Workflow User group in the search bar in Dynamics NAV and click on New. Enter the code and description for it. Insert the approver users with sequence number as 1 2. Create a new Sales Order Workflow Open workflow using the path CRONUS International Ltd./Departments/Administration/Application Setup/Workflow/Workflows Click on New Workflow from Template button from the ribbon. click on the Sales Documents category and select Sales order workflow Here the Sales Order Approval Workflow opens. Click on the first event condition and add a condition on amount > 4000 The response of the first event sets the Sales order status to Pending approval, creates and sends the approval request to the approvers. 3. Set the Approver Type to Workflow User group  We are using the approval type as workflow user group hence, we need to specify this group in the workflow. Now click on the assist edit button of the first response and click on the third response line. By default the approver type is Salesperson/Purchaser Select the Workflow User group from the Approver Type drop down and select the workflow user group code. Now the approval request will be directly sent to the Workflow User group with code SALES MANAGER 4. Set the sales order workflow condition Click on the second event ‘An approval request is approved’. Here we observe that the condition reads Pending approval :0 which means that when all the approver users approve the request i.e. when the the count of the pending approval is 0 then according to the response, release the document. Now we want even if one of the approver users approves the request, the sales order document must be released. we’ll have to change the condition to Pending approval :1 Here when the approval request is sent to both the sales managers, the pending approval count is 2. Now when one of the sales manager approves the sales document the count decreases to pending approval:1hence when the one of the sales manager approves the sales order document the sales order is Released Finally enable the workflow 5. Send an sales order approval request Navigate to sales order and create a sales order greater than 4000 and click on send approval request. Observer the status of the sales document changes to Pending Approval. Login Microsoft Dynamics NAV with the sales manager user credentials and navigate to ‘Request to Approve’ To view the sales order click on Open Record To approve the order click on Approve. This will Release the sales order document. To reject the order click on Reject. This will change the status to Open. Comments can be added by clicking on comments. The sales manager approves it and the document is approved thus the status changes to Released Conclusion: To summarize everything, create a sales order workflow from the template. Create a workflow user group and assign sequence number to 1. Set the condition of amount > 4000 and Pending approval to 1. Select approver type as Workflow user group and select the workflow user group code. Finally enable the workflow.

Introduction: In a scenario where a company uses Excel to keep the data and wants to move its ERP to Dynamics NAV.  A lot of data needs to be added in NAV in order to get a full system working. Thus, copying each entry could be a time-consuming task. Microsoft Dynamics NAV is enabled with the feature to Import and Export Data to and from Excel. Procedure: Ways to Import Export Data from Microsoft Dynamics NAV to Excel There are two ways to Import Export Data to and from NAV Using XMLPORT(Server Side) Using Configuration Packages(Client Side) XMLPORT Method Steps: 1. Create a new XMLPORT in NAV Server Object Designer Window 2. Adding Entries in the XML Port NodeName: Root > Node Type: Element > Source Type: Text > Data Source: <Root>(By Default) NodeName: Table Name(Anyname is fine) > NodeType: Element > SourceType: Table > Data Source: Table(Select the Table click on the Rollup Button) NodeName:Field Name > NodeType: Element > SourceType: Field > Data Source: Field(Select from the Rollup) 3. Indent the Entries as Root(Indent: 0) > Table(Indent: 1) > Fields(Indent :2) 4. Changing the properties of the XMLPORT Delimiter: <‘’> Separator: <TAB> 5. Change the Properties of the Table Format: Variable Text AutoUpdate: Yes AutoReplace: No 6. Save the XMLPORT and RUN For the first time Choose the Direction as ‘Export’ > Save > Filename.xls 7. Open the file, make change the entries and close the file 8. Run the XMLPORT and choose direction as ‘Import’ and select the file Verify whether the import is successful by checking the entries in the table. IMPORT EXPORT using Configuration Packages 1. >Open the Microsoft Dynamics NAV (Client Application) and search Configuration Packages. 2. Create a New Configuration Packages > Enter the following values in required fields as Code: 123(Appropriate Number) and Package Name: Excel Import(Appropriate Name) > Select the Table ID:50001(Using Drop Down) and Table Details will be updated. 3. Under the ‘Tables’ ribbon click on Excel > Export to Excel > Save as appropriate file 4. Open the Excel File and change the entries 5. From the ‘Tables’ ribbon, select Import from Excel and Select the file 6. By this time the data is not written to the table just imported. Thus have to apply the data. After applying, it gives the data inserted or modified or errors if any. Conclusion: The fields are mapped first, thus all the fields to be Imported and Exported are to be known first. Only one excel file per table can be used. The file extension needs to be .xls and not .xlsx as it gives an encoding error while opening the file. Importing or Exporting computed fields cannot be done by this method.

There’s no compelling reason to enter similar information again and again to different frameworks. At the point when you enter information into one framework, information naturally synchronizes to your different frameworks as characterized by your standards. Consider item data in NAV synchronizing to your webstore, online requests adjusting to NAV, and delivery and following information matching up to your webstore. Computerization spares you time since by dispensing with the requirement for you to enter information yourself.  Another significant advantage of microsoft dynamics nav upgrade is that it improves your information quality. Your information won’t be inclined to human mix-up like mistakes and erroneous spellings. Coordination guarantees that quality information makes it to the entirety of your frameworks. Introduction: To show visual representation of aggregated data in Microsoft Dynamics NAV client, tiles are created in NAV which are called Cues. Cues are more user-friendly. It helps the user to get quick details of aggregated data like the total number of open sales orders, total number of customers with a particular status, etc. Pre-Requisite: Microsoft Dynamics NAV Purpose: In this article, I am going to demonstrate the procedure to create a custom Cue based on a query in Dynamics NAV. The scenario which I am going to elaborate is the numbers of contracts which is a custom entity repossessed in the current month. Procedure: I have created a field ‘Status’ in my custom table ‘Contracts’ which is an option field which has the following OptionString ‘Created,Active,Terminated,Ended,Repossessed,Switched’. Now I am creating a cue to find the total number of contracts repossessed in the current month that means the total number of contracts for which status has been changed to ‘Repossessed’ in the current month. I have created two fields in ‘Contracts’ table viz. ‘Repossessed month’ and ‘Repossessed Year’ which will get populated with the Month name and the Year when the Contract status has been changed to ‘Repossessed’ respectively. The next step is to create a query. I have created a query ‘CF_RepossessedMonthQuery’ which will give the count of the total number of contracts repossessed in the current month. The result of the query is as follows: Now create a field in a new table which will store the count of the number of repossessed contracts in the current month. For this, I have created a new field in a table ‘RepossessedContractsMonth’ of DataType ‘Integer’  Navigate to C/AL globals and create two new functions as below:  a. ‘ContractsRepossessedThisMonth’ with Return Value Name ‘CountContracts’ and ReturnType ‘Integer’ and the following local variables. Navigate to properties and set the local property of this function to ‘No’. Go to C/AL code and add the following code for this function: ‘DrillDownContractsRepossessedThisMonth’ with the following local variables:  Navigate to properties and set the local property of this function to ‘No’. Go to C/AL code and add the following code for this function: ‘DrillDownContractsRepossessedThisMonth’ is created so that on clicking the cue the respective records open in a list. The next page is to add the field created in step 4. Create a new group in a page with subtype ‘CueGroup’ Go to C/AL code and in OnOpenPage() add the following code: In OnAfterGetRecord() add the following code:Assign the function created in step 5.a to the field added in the page ‘RepossessedContractsMonth’. In OnDrillDown() of RepossessedContractsMonth add the following code which will call the function created in step 5.b. Save the changes and run the page created in step 6. The output looks like below: On clicking the ‘Contracts Repossessed this Month’ Cue the 2 respective contracts are displayed whose status has been changed to ‘Repossessed’ in the current month. You can add these cues to any standard role center page like Business Manager Role Center, Sales Manager Role Center, etc.  so that the cues are visible when the user opens the NAV client. Conclusion: Using the above procedure, custom cues can be created in Dynamics NAV which will be displayed.

Introduction: Workflows are a list of steps, each step consists of workflow events, workflow condition and workflow responses. Companies require documents to be approved before they can be released or sent to the customers, vendors etc. E.g If a Purchase order has total amount above 10000, an approval may be required from the hierarchy before sending it across the Vendor. here, we use approval workflow Workflow connects business-process tasks performed by different users. The task can be automatic posting, user tasks or approvals. In this blog I’ll be covering the step-wise procedure to set up approval workflow and explain the process of approval workflows. Pre-requisites: Microsoft Dynamics NAV 2017 Steps: 1. SMTP Mail Setup: Browse SMTP Mail Setup in the search bar. Click on ‘Apply Office 365 Server Settings’. This will populate the SMTP Server , SMTP server port and Authentication is set to Basic. In the User ID enter the default email id through which emails will be sent. Enter the password for the email id set. 2. Approval User Setup Approval user setup is based on the user set up. In the user setup we define users, their limit amount based on their hierarchy and who should approve. We can assign substitute approvers when the direct approvers cannot approve for some reason. We can assign email-id of the approvers. Approval Administrator – this user administers the whole approval process Below is a scenario for Sales order approval. For an approval workflow we need to setup Approval User Setup In the above image there are four users CHRISDSILVA, TEST, MANAGER, CEO The CHRISDSILVA user initiates initiates the approval process for the Sales amount from limit 4000 and above and Purchase amount limit 1000 and above, Request amount limit 1000 and above and TEST will approve it The TEST user initiates the approval process for the Sales amount from limit 7500 and above and Purchase amount limit 1500 and above, Request amount limit 1500 and above and MANAGER will approve it The MANAGER user initiates the approval process for the Sales amount from limit 15000 and above, Purchase amount limit 1000 and above, request amount limit 1000 and above and CEO will approve it. The CEO user has Unlimited sales amount, unlimited purchase amount and unlimited request amount and is the Approval administrator. Click on approval user setup test to check whether the setup is correct. This will run and give the status if the status is correct 3.Notifications set up Click on Notification setup for each user to notify the users in the approval process through note or email. A schedule can also be set up to send the notifications daily, weekly, monthly on a particular time. 4. Workflow setup Browse to workflow from the search bar or to the path CRONUS International Ltd./Departments/Administration/Application Setup/Workflow/Workflows, Click on New workflow from Template. This will prompt to select a workflow category. Select the category eg. Sales document and then select a workflow template eg. Sales order workflow This will open the Sales order workflow Template. The first event is approval of the sales document is requested and the condition is that the document type is Order and status of the document is Open then a list of responses will be executed. First Event Click on the Assit edit button on the Add record restriction line, this will open up the response window. This response will do the following Add record restriction Set document status to Pending Approval : This changes the status of the document in this case the sales document status to Pending Approval. Create an approval request for the record using approver type Salesperson/Purchaser and approver limit type Approver Chain. Click on the third response, a option for selected response window opens. Select the approver type depending upon the requirement – Approver, Salesperson/Purchaser, Workflow User Group. The Due date formula is used to send overdue approval mails after the due date mentioned. The delegate after can be set if the document is not approved then it can be delegated to the substituted approver either never, after 1 day, 2 days, 5 days. Approver type: The approver type can select between Salesperson/purchaser, Approver, workflow user group. Here workflow user group is group of users e.g sales department or purchase manager that must approve. Approver means the approver set up done in the previous step or the system approve based on the salesperson/purchaser that are using sales and purchase document. Approver Limit Type: Options like Approver chain, direct approver, First Qualifier approver, Specific approver. Approver chain: if we have multiple approvers then everyone will get an approval request immediately. E.g. if a user creates sales order which not only exceeds his/her limit but also the limit of the direct approver then approval will be required not only from the Direct approver but also from the hierarchy above the Direct approver. These users will receive an approval request in the approval chain. Direct Approver: here only the Direct approver will receive the approval request First Qualifier Approver: Here if the user creates a sales order which exceeds not only his/her limit but also the limit of the Direct approver then an approval request is directly sent to the hierarchy above the Direct approver. Specific Approver: here we can set a user ID to which the approval request will be send. Send approval request for the record and create a notification. An approval request is sent and a notification is created based on the notifications settings. Second Event An approval request is approved that means all users have approved the approval request so the system checks whether the Pending approvals is 0 then in the response all record restrictions are removed and the document is released. Third Event If the system rechecks and the Pending approval is greater than 0 i.e some approver users have not approved the approval request then again a approval request is sent and a notification is created. Fourth Event An approval request is rejected- The approval request … Continue reading Approval Workflow Setup and Process in Microsoft Dynamics NAV 2017 →

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.