Guard signature swap against uninitialized temp records

[Copilot]

LastSignatureTMP.Modify() could run before LastSignatureTMP referenced an inserted temporary PVS Job Signatures row. This happens because the build order is cover-first, so the first processed item is not guaranteed to be the residual sheet ("Entry No." = 1).

• Root cause

  • The residual-sheet swap logic assumed LastSignatureTMP had already been initialized.
  • In both custom Build_Entries implementations, that assumption is false when a non-residual item is processed first.

• Change

  • Added an explicit initialization guard before entering the swap path.
  • If no prior signature has been captured yet, the current temp record becomes LastSignatureTMP instead of attempting a Modify() on an uninitialized record.

• Scope

  • BuildSignatures/PTEBuildSignatures.CodeUnit.al
  • Planning Board - ToolTip Performance/PTETooltip.CodeUnit.al

• Behavioral effect

  • Preserves the existing residual-sheet reordering behavior once a baseline signature exists.
  • Avoids intermittent runtime failures caused by modifying a temp record with no current row.

if (JobItemTMP."Entry No." = 1) or (not LastSignatureInitialized) then begin
    LastSignatureTMP := out_RecTmp;
    LastSignatureInitialized := true;
end else begin
    out_RecTmp."Assembly Order" := LastSignatureTMP."Assembly Order";
    out_RecTmp.Indent := LastSignatureTMP.Indent;
    out_RecTmp.Modify();

    LastSignatureTMP."Assembly Order" := AssemblyOrder;
    LastSignatureTMP.Indent := Indentation;
    LastSignatureTMP.Modify();
end;

Original prompt

line 223 LastSignatureTMP.Modify(); can sometimes fail please se is you can find why you will need to look in the PrintVis app in the .alpackages folder

Created from VS Code.