11 lines
No EOL
3.1 KiB
XML
11 lines
No EOL
3.1 KiB
XML
<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Readability on AL Guidelines</title><link>https://alguidelines.dev/bcbestpractices/readability/</link><description>Recent content in Readability on AL Guidelines</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><atom:link href="https://alguidelines.dev/bcbestpractices/readability/index.xml" rel="self" type="application/rss+xml"/><item><title>Unnecessary 'else'</title><link>https://alguidelines.dev/bcbestpractices/readability/unnecessary-else/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/bcbestpractices/readability/unnecessary-else/</guid><description>&lt;Created by Microsoft, Described by waldo&gt;
|
|
Description else should not be used when the last action in the then part is an exit, break, skip, quit, error.
|
|
Bad code procedure SomeProcedure() begin if IsAdjmtBinCodeChanged then Error(AdjmtBinCodeChangeNotAllowedErr,...) else Error(BinCodeChangeNotAllowedErr,...); end; Good code procedure SomeProcedure() begin if IsAdjmtBinCodeChanged then Error(AdjmtBinCodeChangeNotAllowedErr,...) Error(BinCodeChangeNotAllowedErr,...); end; Discussions You can find discussions on all &ldquo;Best Practices&rdquo; here.
|
|
If you don&rsquo;t find the discussion of this guideline, please feel fee to create a new one with the same title as this article.</description></item><item><title>Variable Naming</title><link>https://alguidelines.dev/bcbestpractices/readability/variable-naming/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/bcbestpractices/readability/variable-naming/</guid><description>&lt;Created by Microsoft, Described by waldo&gt;
|
|
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.</description></item><item><title>Variables Declarations Order</title><link>https://alguidelines.dev/bcbestpractices/readability/variables-declarations-order/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/bcbestpractices/readability/variables-declarations-order/</guid><description>&lt;Created by Microsoft, Described by waldo&gt;
|
|
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 &ldquo;Best Practices&rdquo; here.</description></item></channel></rss> |