https://alguidelines.dev/bcbestpractices/readability/Recent content in Readability on AL GuidelinesHugo -- gohugo.ioen-ushttps://alguidelines.dev/bcbestpractices/readability/variable-naming/Mon, 01 Jan 0001 00:00:00 +0000https://alguidelines.dev/bcbestpractices/readability/variable-naming/<Created by Microsoft, Described by waldo> Description Variables that refer to a AL object must contain the objects name, abbreviated where necessary. A variable must begin with a capital letter. Blanks, periods, and other characters (such as parentheses) that would make quotation marks around a variable necessary must be omitted. If a variable is a compound of two or more words or abbreviations, each word or abbreviation should begin with a capital letter.https://alguidelines.dev/bcbestpractices/readability/variables-declarations-order/Mon, 01 Jan 0001 00:00:00 +0000https://alguidelines.dev/bcbestpractices/readability/variables-declarations-order/<Created by Microsoft, Described by waldo> Description Variables declarations should be ordered by type. In general, object and complex variable types are listed first followed by simple variables. The order should be: Record Report Codeunit XmlPort Page Query Notification BigText DateFormula RecordId RecordRef FieldRef FilterPageBuilder (Ref: Microsoft Docs) Bad code StartingDateFilter : Text; Vendor : Record Vendor; Good code Vendor : Record Vendor; StartingDateFilter : Text; Discussions You can find discussions on all “Best Practices” here.