bcquality/custom/knowledge/patterns/cmfrt-interface-injection.bad.al
BeytullahCengiz88 afb1fa2883 Add CMFRT naming conventions, object ID ranges, and patterns documentation
- 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.
2026-07-14 14:09:04 +02:00

12 lines
434 B
AL

// Monolithic entry-point: the implementation is embedded, there is no interface,
// and there is no OnBefore event. Dependent extensions cannot override the
// calculation without an AL override hack.
table 2045090 "CMFRT MS Measure State"
{
procedure CalcTotals()
begin
// All calculation logic is hard-coded here.
Rec."Total Amount" := Rec."Line Amount" + Rec."Tax Amount";
Rec.Modify();
end;
}