The world changes constantly. So do the way companies work and the way they interact with other companies.

A changing company may require functional changes on their Microsoft Dynamics NAV implementation. A whole new project should start. It may not be an implementation project, but some of the steps that have to be taken on an implementation project also apply. There are some other things to take into account though, and this chapter will explain how to handle a project like this one by analyzing the actions to be performed by using four examples of a functional change in Dynamics NAV:

General guidelines

All functional changes are different. Some will just require a few actions to complete the change; some others may require many actions, not just on the functionality being changed, but also somewhere else. There are a few things you have to take into account when implementing a functional change. In this section we will provide some general guidelines. Later on, we will follow the guidelines for all the examples of the chapter.

The following figure shows the general steps that will have to be performed to implement a functional change:

1. The first step is to clearly define the functional change.
2. After that, we have to think about how this change will affect other Dynamics NAV functionalities and whether those other functionalities will have to change somehow.
3. Once all the changes are clear, we will have to define a clear list of all the actions that will have to be completed to be able to implement the functional change.
4. Having the whole picture of the effort required to implement the functional change, we will be able to choose the right time to actually implement the change.
5. And finally, plan everything so that all actions are completed on time and the functional change can be implemented on the chosen day.