Why doesn't copying project planning lines reset their picked quantity?

cegekaJG
cegekaJG Member Posts: 6
in NAV Three Tier

I noticed that when copying project tasks to a new project in Business Central 25.2, the copied planning lines won't reset their fields related to their warehouse pick ("Qty. Picked", "Completely Picked" etc). I thought this was a bug, but even 25.12 has this behavior.

This occurs in the codeunit Copy Job, specifically the procedure CopyJobPlanningLines. Here is the relevant code:

TargetJobPlanningLine.Init();

TargetJobPlanningLine.Validate("Job No.", TargetJobTask."Job No.");

TargetJobPlanningLine.Validate("Job Task No.", TargetJobTask."Job Task No.");

if NextPlanningLineNo = 0 then

    NextPlanningLineNo := FindLastJobPlanningLine(TargetJobPlanningLine);

NextPlanningLineNo += 10000;

TargetJobPlanningLine.Validate("Line No.", NextPlanningLineNo);

TargetJobPlanningLine.TransferFields(SourceJobPlanningLine, false);

if not CopyPrices then

    TargetJobPlanningLine.UpdateAllAmounts();


TargetJobPlanningLine."Remaining Qty." := 0;

TargetJobPlanningLine."Remaining Qty. (Base)" := 0;

TargetJobPlanningLine."Remaining Total Cost" := 0;

TargetJobPlanningLine."Remaining Total Cost (LCY)" := 0;

TargetJobPlanningLine."Remaining Line Amount" := 0;

TargetJobPlanningLine."Remaining Line Amount (LCY)" := 0;

TargetJobPlanningLine."Qty. Posted" := 0;

TargetJobPlanningLine."Qty. to Transfer to Journal" := 0;

TargetJobPlanningLine."Posted Total Cost" := 0;

TargetJobPlanningLine."Posted Total Cost (LCY)" := 0;

TargetJobPlanningLine."Posted Line Amount" := 0;

TargetJobPlanningLine."Posted Line Amount (LCY)" := 0;

TargetJobPlanningLine."Qty. to Transfer to Invoice" := 0;

TargetJobPlanningLine."Qty. to Invoice" := 0;

TargetJobPlanningLine."Ledger Entry No." := 0;

TargetJobPlanningLine."Ledger Entry Type" := TargetJobPlanningLine."Ledger Entry Type"::" ";

OnCopyJobPlanningLinesOnBeforeTargetJobPlanningLineInsert(TargetJobPlanningLine, SourceJobPlanningLine);

TargetJobPlanningLine.Insert(true);

It looks like the fields aren't being reset on purpose, but why? Since the system can only find related warehouse activity by looking for the planning line's primary key, there will be no activity despite the line saying otherwise.

Am I missing something, or is this a bug that hasn't been fixed?

Answers

  • joostheger
    joostheger Member Posts: 22

    You mean that Quantity Picked is missing here? Is that a field of the table Job Planning Line, or does it come from somewhere else? You might take a look in the table, maybe you can find a lead there?

  • cegekaJG
    cegekaJG Member Posts: 6

    @joostheger "Quantity Picked" is a field of the table "Job Planning Line". The problem is that it's not being reset when copied, causing BC to incorrectly report that the line already has picked quantities.

  • RockWithNAV
    RockWithNAV Member Posts: 1,198

    Hey Buddy @cegekaJG ,

    Seems some top custom code might be impacting this, system will never copy Qty Picked. Still I tried attempting the same and behavior was all as expected. See the first one was original and last 3 copied one -

    image.png
    Thanks

    Blog - rockwithnav.wordpress.com/
    Twitter - https://twitter.com/RockwithNav
    Facebook - https://facebook.com/rockwithnav/
  • cegekaJG
    cegekaJG Member Posts: 6

    @RockWithNAV, like I said, the scenario is copying project tasks to a new project, not the same one. Also, the default code implicitly copies the field "Qty. Picked" when using the following command:

    TargetJobPlanningLine.TransferFields(SourceJobPlanningLine, false);

    The code has to reset the fields explicitly, otherwise they will be identical to those of the original line. Since the field in question isn't being addressed, it should be the same, right?

Categories