Changing the definition of a table can lead to data loss in NAV2013R2


Well this is fun.

As the time goes by since the release of NAV2013R2, some bugs have been found. These bugs were not that big of a deal for the most part.

Now, when we get into losing data this is a different story. This means that best case scenario nothing happens and mid-to-worst case scenario you start praying you have an updated backup.


The issue briefly explained consists of:

During the development of NAV, specifically during the modification of a the tables structure of the application, if certain circumstances ocurred, the info contained in that very same table could be lost partially or completely.


For those of you who are curious, here you have a link from the Dynamics NAV Blog explaining the issue in depth:



Microsoft published the hotfix (also included in the corresponding Cumulative Update) a few months ago.

List of NAV2013R2 Plataform Hotfixes 

Specific hotfix to fix this issue

Once you have downloaded it and unzipped, you will find a few folders inside. They are part of the update for both the client and the service. When you update the service keep in mind it must be STOPPED or you might face further problems

I leave here the table explaining each of the folders:


Type Nombre Tier Default Path
Application Update APPLICATION Object Designer – Requires Merge
Platform Update ADCS Client (3 tier) C:\Program Files (x86)\Microsoft Dynamics NAV\71\Automated Data Capture System
Platform Update NST Service (2 tier) C:\Program Files\Microsoft Dynamics NAV\71\Service
Platform Update OUTLOOK Client (3 tier) C:\Program Files (x86)\Microsoft Dynamics NAV\71\OutlookAddin
Platform Update RTC Client (3 tier) C:\Program Files (x86)\Microsoft Dynamics NAV\71\RoleTailored Client
Platform Update WEB CLIENT Service (2 tier) C:\Program Files\Microsoft Dynamics NAV\71\Web Client


Keep in mind when installing the hotfix…

You will probably need to convert the database (this will happen when you open the database with the most updated version of the development environment). If this happens you will also need to update the workstations (clients) to be able to connect to the converted database.



Leave a Comment.