Full article: http://blogs.msdn.com/b/nav/archive/2014/02/28/important-information-potential-data-loss-in-nav2013r2.aspxMSDN NAV Blog wrote: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.
[…]
Comments
In my opinion it's a quite restrictive constraint, what do you think about?
Moreover I'm thinking about databases with 24/7 (like my production ones) web services, need to be stopped as well?
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
Marketing wants to target NAV to smaller companies - who typically want their changes done on the fly and developers / consultants backup and restore companies because it is quick because of size.
Development wants to put in more big company controls suitable to large ERP implementations.
Maybe marketing and development should get together and agree on direction.
If they had told us at Directions that backup and restore company was going away plus the ability to make changes to live installs, they would have had a strong negative response.
http://mibuso.com/blogs/davidmachanick/
Source German NAV Developers Blog.
However, just because NAV allows you to make changes to a live system doesn’t mean that a Developer should.
Bug or no bug we’d never recommend modifying a system whilst users are in the system.
If you have users or a NAS on the system and you modify it they will keep running on old versions of application objects from the cache and they will continue doing it until the objects get out of scope, which for a NAS could mean never or until the NST is restarted.