bcquality/custom/knowledge/architecture/cmfrt-calls-from-base-table-only.good.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

37 lines
1.3 KiB
AL

// Subscriber codeunit calls the BASE TABLE procedure — not the implementation codeunit.
codeunit 2045720 "CMFRT BA Sales Subscribers"
{
[EventSubscriber(ObjectType::Codeunit, Codeunit::"Sales-Post", 'OnAfterPostSalesDoc', '', false, false)]
local procedure CMFRTBAOnAfterPostSalesDoc(var SalesHeader: Record "Sales Header")
var
CMFRTBAItem: Record "CMFRT BA Item";
begin
// Route through the base table — integration events fire normally.
CMFRTBAItem.CMFRTBASyncPostedSalesDoc(SalesHeader."No.");
end;
}
// Base table owns all entry points to implementation codeunits.
table 2045095 "CMFRT BA Item"
{
procedure CMFRTBASyncPostedSalesDoc(SalesDocNo: Code[20])
var
SyncImpl: Codeunit "CMFRT BA SyncPostedDoc Impl";
Handled: Boolean;
begin
OnBeforeCMFRTBASyncPostedSalesDoc(SalesDocNo, Handled);
if Handled then
exit;
CMFRTBASyncPostedSalesDoc(SyncImpl);
end;
procedure CMFRTBASyncPostedSalesDoc(SyncImpl: Interface "CMFRT BA ISyncPostedDoc")
begin
SyncImpl.CMFRTBASyncPostedSalesDoc(Rec);
end;
[IntegrationEvent(false, false)]
local procedure OnBeforeCMFRTBASyncPostedSalesDoc(SalesDocNo: Code[20]; var Handled: Boolean)
begin
end;
}