bcquality/custom/knowledge/breaking-changes/cmfrt-never-delete-always-obsolete.good.al
BeytullahCengiz88 c72c0ad685 Add CMFRT coding standards documentation and examples
- Introduced guidelines for "one codeunit one global function" architecture to enforce single responsibility in AL code.
- Added best practices and anti-patterns for adding parameters via overloads to maintain backward compatibility.
- Documented the importance of never deleting members in AL and always marking them as obsolete.
- Established the requirement for OnBefore and OnAfter integration events for global procedures to enhance extensibility.
- Defined naming conventions for CMFRT objects, including prefixes and object ID ranges to avoid conflicts.
- Implemented patterns for case statements to ensure all cases are handled, including the necessity of an else clause.
- Introduced the interface injection pattern to allow pluggable operations in table-level code.
- Recommended using Confirm Management for user confirmations to improve testability.
- Established a three-permission set pattern for security to ensure proper access control.
- Created a review skill for CMFRT AL standards to automate compliance checks against established guidelines.
2026-07-02 13:12:09 +00:00

23 lines
798 B
AL

// Obsoleted field kept at the end of the table — never deleted.
table 2045085 "CMFRT GD Setup"
{
fields
{
field(1; "Primary Key"; Code[10]) { DataClassification = SystemMetadata; }
field(2; "CMFRT GD ErrorPath"; Text[500])
{
Caption = 'Error Path';
DataClassification = CustomerContent;
}
// Obsolete section at the end — original field retained with state = Removed.
field(2045325; "CMFRT GD Error Path"; Text[200])
{
Caption = 'Error Path (Obsolete)';
DataClassification = CustomerContent;
ObsoleteState = Removed;
ObsoleteReason = 'Replaced by field "CMFRT GD ErrorPath" with extended length.';
ObsoleteTag = 'Task-29100';
}
}
}