Microsoft/alguidelines
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Requested changes

Browse source
This commit is contained in:
waldo1001 2021-12-13 16:31:51 +01:00
parent a1438deb71
commit d5f6816829
1 changed files with 18 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

19
content/BCBestPractices/Readability/variables-declarations-order/index.md
View file

@ -6,7 +6,24 @@ weight = 1430
<_Created by Microsoft, Described by waldo_\> <_Created by Microsoft, Described by waldo_\>
## Description ## 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 **the same as the object list in the object designer for AL objects**. Afterwards come the complex variables like RecordRef, .NET, FieldRef etc. At the end come all the simple data types in no particular order. 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](https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/analyzers/codecop-aa0021))
## Bad code ## Bad code