Done
Details
Assignee
Siarhei HrabkoSiarhei HrabkoReporter
Andrei MakarankaAndrei MakarankaLabels
Priority
P3Story Points
0Sprint
NoneDevelopment Team
ThunderjetFix versions
Release
R3 2021 Bug FixTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Siarhei Hrabko
Siarhei HrabkoReporter
Andrei Makaranka
Andrei MakarankaLabels
Priority
Story Points
0
Sprint
None
Development Team
Thunderjet
Fix versions
Release
R3 2021 Bug Fix
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created November 24, 2021 at 8:40 AM
Updated December 1, 2021 at 6:56 PM
Resolved November 24, 2021 at 11:45 AM
Overview:
When a piece location is changed in the Receiving app, it works if a piece is edited, but fails to work properly if the location is changed during the receiving process. In this case, the
locationId
is added to the piece, but theholdingId
is not updated.Steps to Reproduce:
Create order + line with a given location (createInventory = instance, holding, item)
Open the order
Receiving app - open the title and click on Receive button
Select the line
Click on "Create new holdings for location"
Choose another location and click on "Save and Close"
Click on Receive button
After the dialog closes, click on the piece in the list
Expected Results:
The piece has the right new location.
Actual Results:
The piece displays the old location.
Additional Information:
After receiving, the piece has the new
locationId
but keeps the oldholdingId
.The check-in request uses a null holdingId. Backend is supposed to create the holding (which it does) and save the new holdingId in the piece (which it does not).
Workaround:
Change the piece location before receiving.