Hi All
I want to ask one question. If You want to create new/custom module in Navision, what are mandatory steps/tables that should be taken/created. Ex:master tables, documents… Are new Journals,Ledger Entry , Value Entry are mandatory ?
Is there some general scheme or rules what should contain one module?
BR
There are no mandatory steps as you described them, but you should follow the overall “rules” of NAV architecture and workflow. Of course, from the all possible tables you create only those really required in your module, not all of the possible types you named in your post.
Additional requirements apply, if you intend to create an official NAV AddOn and therefore are going to get it officially registered with MS as such.
Problem is, that in fact normal documents describing these requirements almost do not exist. There was one doc called Navision Architecture, but it is at least 10 years old and hard to find both in official MS sites and other net sources. This document describes the underlying general model of tables structure under what is called an application area in NAV slang. Nevertheless it’s so old it’s still usable, as almost nothing has changed throughout these years.
Good news is, that a team of NAV gurus both from MS and the NAV community maintain a Design Patterns site, it’s a very good source for NAV developers, check it out.
Add-On requirements in addition to table structure itself add naming conventions of everything from tables to fields to variables etc etc and describe the process of registering the AddOn. This documentation can be obtained as soon as you express willingness to register your company as AddOn developer.
P.S. I moved your post to more appropriate forum.