bcquality/custom/knowledge/patterns/cmfrt-use-confirmmanagement.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

15 lines
505 B
AL

codeunit 2045750 "CMFRT GD Deletion Handler"
{
procedure CMFRTGDDeletePOI(POICode: Code[20])
var
CMFRTGDPOI: Record "CMFRT GD POI";
ConfirmManagement: Codeunit "Confirm Management";
DeleteConfirmQst: Label 'Delete POI %1?', Comment = '%1 = POI Code';
begin
if not ConfirmManagement.GetResponseOrDefault(StrSubstNo(DeleteConfirmQst, POICode), false) then
exit;
if CMFRTGDPOI.Get(POICode) then
CMFRTGDPOI.Delete(true);
end;
}