Getting structure into the documentation
Putting our pieces together now, gives us a database for storing the help, an editor (MarkdownPad) for editing, and a converter (Pandoc) for performing conversion
Putting our pieces together now, gives us a database for storing the help, an editor (MarkdownPad) for editing, and a converter (Pandoc) for performing conversion
Help text can either be content specific (help to a specific field) or general. With NAV the requirement for content specific help is mandatory, users
Back in the “old” days, developing for NAV / Navision / Financials / Attain etc.. was easy. You needed the FIN.EXE (for FINSQL.EXE) and database,
UPDATE: If you need a control for Business Central in AL look here In Dynamics NAV 2013 R2 and 2015 there is a new format
In NAV 2013 R2, if a RecordRef does not have a active record, CURRENTKEYINDEX will return -1. IN NAV2009 and older, the value was 1
In NAV2009 and earlier, GLOBALLANGUAGE(0) would set the language in NAV to the “default” language of the classic client. This undocumented feature does not work
support@hougaard.com or
through Twitter on @eHougaard
Hougaard.com – Software
927 Canyon Blvd
North Vancouver, BC, V7R2J9
Canada