bcquality/custom/knowledge/patterns/cmfrt-validate-not-assign.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

14 lines
701 B
AL

codeunit 55029 "CMFRT AQ FS Job Creator"
{
local procedure CMFRTAQFillJobFromBuffer(var WorkOrderBuffer: Record "CMFRT AQ FS WO Buffer"; var Job: Record Job)
begin
Job.Init();
Job."No." := WorkOrderBuffer."CMFRT AQ No.";
// Direct assignment skips OnValidate: dependent fields stay empty,
// posting-group checks and field subscribers never run.
Job.Description := WorkOrderBuffer."CMFRT AQ Description";
Job."Sell-to Customer No." := WorkOrderBuffer."CMFRT AQ Sell-to Customer No.";
Job."Ship-to Address" := WorkOrderBuffer."CMFRT AQ Ship-to Address";
Job."Location Code" := WorkOrderBuffer."CMFRT AQ Location Code";
end;
}