The world changes constantly, therefore, the demands for every company that's interested to keep doing business will need to change with it.
A company may require functional changes on their Microsoft Dynamics NAV implementation as more and more demands from external parties they do business with. The new project 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 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:
- The Requisition Worksheet
- Fixed Assets
- Item Tracking
- Extending a customized functionality
Depending on the requirement, the functional changes will be different. Some will just require a few actions to complete the change; others may require many actions, which is not just on the functionality being changed. There are a few things 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 should be performed to implement a functional change:
- The first step is to clearly define the functional change
- Think about how this change will affect existing Dynamics NAV functionalities and whether those functionalities will need to be changed as well
- Define a list of all the actions that will have to be completed to be able to implement the functional change
- Choose the right time to implement the change
- Actually implement the change into the system