You may experience data loss in Microsoft Dynamics NAV 2013 R2 in the following situations, separately or in combination:
- Changing an application object more than once, for example by two different developers, in the same database connected to the same Microsoft Dynamics NAV Server instance while users are working in the system.
- Compiling all application objects, and thereby potentially changing objects more than once, in a database that is connected to a Microsoft Dynamics NAV Server instance that users are accessing.
To avoid the problem, we advise that you work according to the following best practices:
- Application developers must be working on their own database and connect to their own Microsoft Dynamics NAV Server instance. When you deploy changes to the live production database, make sure that no users are working in the system.
- You must compile objects only when no users are working in the system, including users connecting through NAS.
With update rollup 5 for Microsoft Dynamics NAV 2013 R2 – KB 2937999, this issue has been fixed and you do not have to take the precautions described above. However, we still advise that you separate development from production databases.
Please note that implementing update rollup 5 will require a database conversion.
We're always looking for feedback and would like to hear from you. Please head to the Dynamics 365 Community to start a discussion, ask questions, and tell us what you think!