Navision Coding Standards

HariharanssudanHariharanssudan Member Posts: 26
Hi to Everybody,

I am very new to Navision.

I would like to see Navision Coding standards and Naming standards. If anybody having the same, Kindly send me to my id (hariharanssudan@yahoo.com)

Thanks in Advance,
Hari

Comments

  • FCPFCP Member Posts: 36
    Definitely a god idea. I never heard of something being done for NAVISION ?!

    Personally I consider much more “readable” the use of of a prefix for variables of some kind. Is not as important as good comment lines but helps.

    I use the following Prefixs
    Rec - Record
    Unit - CodeUnit
    Par – parameter in a function
    G – Global Variables
    P – Private Variable
    Aut - Automation

    This is just my personal an example
  • Luc_VanDyckLuc_VanDyck Member, Moderator, Administrator Posts: 3,633
    A while ago, the same subject has been discussed: Navision naming conventions
    No support using PM or e-mail - Please use this forum. BC TechDays 2024: 13 & 14 June 2024, Antwerp (Belgium)
  • Alex_ChowAlex_Chow Member Posts: 5,063
    A long while back before Navision was bought by Microsoft, they give a manual or booklet on the coding standards. I'm not sure if they still provide that now.

    Basically, to follow the Navision standard, use the same "look and feel" as the existing codes.
  • ShenpenShenpen Member Posts: 386
    Hariharanssudan: why don't you just look at the code, f.e. Codeunit 80?

    FCP: and does it really help you in any way? Wow, I'm amazed. Charles Simonyi designed H.N. for completely different purposes: notating the purpose of variables and not just simply types. In standard Navision, variables like OldValueEntry and NewValueEntry are a lot closer to the concept of H.N. than f.e. recValueEntry would be.

    Do It Yourself is they key. Standard code might work - your code surely works.
Sign In or Register to comment.