Creative plagiarism and patterns
When we want to create new functionality, the first task is obviously to create functional specifications. Once those are in hand, we should look for guidelines to follow. Some sources which are readily available are:
- The NAV Design Patterns Wiki (https://community.dynamics.com/nav/w/designpatterns/default.aspx)
- C/AL Coding Guidelines as used internally by Microsoft in the development of NAV application functionality (https://community.dynamics.com/nav/w/designpatterns/156.cal-coding-guidelines.aspx)
- Blogs and other materials available in the Microsoft Dynamics NAV Community (https://community.dynamics.com/nav/default.aspx)
- The NAV system itself is always good to start with an existing pattern or object that has capabilities similar to our requirements and study the existing logic and the code. In many lines of work, the term plagiarism is a nasty term. But when it comes to modifying an existing system, plagiarism is a very effective research and design...