bcquality/custom/knowledge/architecture/cmfrt-buffer-table-api-pattern.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

15 lines
526 B
AL

page 55035 "CMFRT AQ FS JJL API"
{
PageType = API;
SourceTable = "Job Journal Line"; // real table exposed directly to the API
trigger OnInsertRecord(BelowxRec: Boolean): Boolean
begin
// Manual insert/exit boilerplate duplicates the framework insert
// and couples the HTTP request to the real-table insert: no retry,
// no error queue, one validation error fails the whole request.
Rec.Insert(true);
Rec.CMFRTAQFSLogIncomingRequest();
exit(false);
end;
}