New upgrade technology provides easy path to annual NAV releases
Microsoft NAV is the most popular mid-market ERP in the world because of its ability to support unique business processes and accommodate inevitable changes over time. These customizations have always been upgradable although competitors continue to promulgate the idea that modifications condemn you to ERP version-lock, out-of-date and unable to upgrade. The Dynamics NAV integrated development environment and new upgrade technology reinforce the Dynamics NAV value proposition. Microsoft NAV enables organizations to confidently leverage the unique power of NAV with total confidence. You can easily customize NAV and then easily migrate from one annual NAV release to the next. No competitor can match Microsoft’s R&D. The investment in Dynamics NAV is unrivaled. “Eventing” is among the many innovations in Dynamics ERP.
If you wanted to add functionality to existing processes in prior versions of Microsoft Dynamics NAV, you would have to go into the code and make any desired changes there. While this is easy, it means that any time an upgrade comes along, those changes have to be moved over into the new version. That is normally not very difficult but with most NAV installations there are enough modifications that it can significantly affect the time and cost of the upgrade. With the concept of eventing introduced in NAV 2016, many of the changes that are commonly made to NAV can be removed from the base software and put into custom NAV codeunits. This means that during an upgrade, those changes are no longer a factor and can be moved automatically.
Throughout the various processes in NAV, there are now events that will occur during various tasks that NAV performs. An event is really just NAV saying “I’m doing XYZ, does anyone need me to do something else first?” Let’s assume XYZ happens to be releasing a sales order. It is normal for there to be additional custom validation performed during a sales order release but rather than adding that to the stock release process, eventing allows us to tell NAV “Yes, please run codeunit 50045 and pass the sales order you’re looking at”. No modifications have been made to the original NAV software but now it sees the event request and runs some custom code. If this code finds a problem with the sales order it’s looking at, it can raise an error just like it would have before and stop the release process. We can also do things like make changes to the sales order or any other associated data. Also, there may be several events raised during any specific task. Going back to the sales order release, we might find an event at the beginning, at some point during the middle and at the end of the process. The event subscriptions themselves are just records in a table. They can be treated just like any other data in the database during an upgrade.
While eventing does not completely eliminate the need to modify the base code, it makes a significant dent in the amount of modifications that are needed by providing a way to separate out custom code in many situations. With this and other new upgrade technologies now in NAV 2016, many upgrades can be completely automated and run with little human interaction.
Ready to grow your business? Get your free organizational readiness assessment.