Skip to main content

NAV 2013 R2 - How to Sync Tenant?

Hi all,

A common Command referred in many of the Forums that can be used to Sync Changes of Navision in SQL is Sync Tenant.

Most of us are not aware how to run this command. In this post we will see how to Run and When to Run this Command?

When to Run?

A- When Upgrading Database from NAV 2009 / NAV 2009 SP1 / NAV 2009 R2 to NAV 2013 R2.

After Opening Database in NAV 2013 R2, Compiling System Tables and Importing Merged Objects of NAV 2013 R2.


RUN SYNC Tenant.  

B- When Importing a FOB contain so many objects and Major Changes in Tables.
As SQL stores the data and Table Structure so if you have Major Table Changes in the Imported FOB.
 
RUN SYNC Tenant.

Why to Run?

- With Release of NAV 2013 R2, the changes from Navision to SQL Occurs in Two Cases -

A) Any Client Activity like Opening a Page, Running RTC Client.
B) Running NAV Sync Tenant Command.

I would Still prefer the Way of Sync Tenant as most of the Time While Trying to Update SQL Using Running RTC Client, client get Timeout and operation Fails.

Where to RUN?

Sync Tenant Runs on the Middle Tier (Service Tier) of the Three Tier Architecture?

How to RUN ?

1. OPEN ISE As Administrator.

2. Load the Command Let for NAV 2013 R2.

-----------------------------------------------------
#Prepare PowerShell
Import-Module 'C:\Program Files\Microsoft Dynamics NAV\71\Service\NavAdminTool.ps1'
-----------------------------------------------------

If you Require Assistance in above Steps Refer Here

3. Run the Below Command to Sync Tenant.
-----------------------------------------------------
#Sync Tenant Where Service Name that connect to Database is DynamicsNAV71
Sync-NAVTenant -ServerInstance DynamicsNAV71
-----------------------------------------------------

OR Make as query as shown Below after Step 1 & 2.

3) Refresh the Command Bar and Search for Command Sync-NAVTenant. Specify the Service Instance and Click Run as shown below.



4) On the Status Bar you will see the status of the sync, once the Status Changed to Completed it means that changes from NAV to SQL are completed.


I hope you find the information above useful and will help you while importing last set of objects and during upgrade Process.

Regards,
Saurav Dhyani
www.sauravdhyani.com

Comments

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.