This repository was archived by the owner on Oct 19, 2026. It is now read-only.
Repository navigation
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
A client of ours has been testing their environment after an upgrade from Dynamics NAV 2017 to Business Central 25.2 (on-prem) and they are experiencing problems trying to edit
Job Taskrecords that have been created by copying an existing project.The error occurs due to a check that requires the field
Qty. Pickedof all corresponding Job Planning Lines to be0. After some investigation, I've found that when creating the planning lines, the procedureCopyJobPlanningLinesof the codeunitCopy Job (1006)resets a number of different fields - except some likeQty. Picked.I can't say we are working with a clean slate here - there have been a number of modifications to the warehouse logic, and this client has worked with these changes for years before I've gotten involved, so I'm assuming an unmodified environment wouldn't run into the same issues.
But before I modify the
CopyJobPlanningLinesprocedure, I want to understand why the standard code doesn't reset the field in question and if I am potentially adding a new error with the change.All reactions