mirror of
https://github.com/microsoft/BCQuality.git
synced 2026-08-06 17:36:53 +01:00
afb1fa2883
- Introduced guidelines for using the "CMFRT" prefix in object names, fields, and procedures to avoid naming collisions and ensure clarity. - Established rules for object ID ranges to prevent conflicts with other extensions and maintain historical integrity. - Documented best practices and anti-patterns for various coding patterns, including case statements, interface injection, label usage, and validation methods. - Implemented a standards review skill to evaluate AL source changes against CMFRT company standards, ensuring compliance with naming, permissions, and architectural patterns.
25 lines
694 B
AL
25 lines
694 B
AL
// ID 50000 is outside both defined CMFRT ranges and will conflict with
|
|
// other extensions that follow the standard AppSource free range.
|
|
table 50000 "CMFRT GD POI"
|
|
{
|
|
Caption = 'POI';
|
|
DataClassification = CustomerContent;
|
|
|
|
fields
|
|
{
|
|
field(1; "Code"; Code[20]) { DataClassification = CustomerContent; }
|
|
}
|
|
}
|
|
|
|
// ID 2045081 was previously assigned to a removed object.
|
|
// Reusing it causes silent conflicts with historical telemetry and upgrade codeunits.
|
|
table 2045081 "CMFRT GD New Feature"
|
|
{
|
|
Caption = 'New Feature';
|
|
DataClassification = CustomerContent;
|
|
|
|
fields
|
|
{
|
|
field(1; "Code"; Code[20]) { DataClassification = CustomerContent; }
|
|
}
|
|
}
|