Coding considerations
The most challenging and most important part of an upgrade is porting the code and data modifications from the older version of a system to the new version. When the new version has major design or data structure changes in an area that we have customized, it is quite possible that our modification structure will have to be re-designed and perhaps even be recoded from scratch.
On the other hand, often the changes in the new product version of NAV don't affect much existing code, at least in terms of the base logic. If our modifications are done properly, it's often not difficult to port custom code from the older version into the new version. By applying what some refer to as "low-impact coding" techniques, we can make the upgrade job easier and thereby less costly.
Good documentation
In the earlier chapters, we discussed some documentation practices that are good to follow when making C/AL modifications. Here is a brief list of practices...
