Fail to edit some order lines

Description

Overview:
When trying to edit an open order line, we get an error message. Not for all order lines, but for some.
It tends to be more on older orders (before 3.2?) but I'm not sure about if that is a pattern. Some old orders are possible to edit.
This issue may be related to

Steps to reproduce:
1. Login to Chalmers' FOLIO (version 3.2)
2. Go to Orders and click on order with PO number 10152
3. Scroll down to PO Lines and click on order line 10152-1
4. Edit
5. Make a change in the Receiving note field and click Save

*Expected Result: *
To get a success message and to see the changes.
*Actual Result: *
Changes are not saved.
I get the error message "Purchase order line has not been created"

F12 Console
– (core) Starting Stripes ...
okapi-fse-eu-central-1.folio.ebsco.com/source-storage/formattedRecords/d72e0fe5-b604-48f2-8649-44029f61d73f?identifier=INSTANCE:1 Failed to load resource: the server responded with a status of 404 ()
bundle.80eb86a08fa84218a9df.js:68 MARC record getting ERROR: Object
(anonymous) @ bundle.80eb86a08fa84218a9df.js:68
bundle.80eb86a08fa84218a9df.js:93 – (action) sorted by updatedDate
bundle.80eb86a08fa84218a9df.js:93 – (action) sorted by lastUpdated
bundle.80eb86a08fa84218a9df.js:93 – (action) clicked a4e542ec-39da-4aec-a8a8-64bb6917c0f6, selected record = Object
okapi-fse-eu-central-1.folio.ebsco.com/orders-storage/order-invoice-relns?limit=2147483647&query=purchaseOrderId%3D%3Da4e542ec-39da-4aec-a8a8-64bb6917c0f6:1 Failed to load resource: the server responded with a status of 403 ()
/orders/view/a4e542ec-39da-4aec-a8a8-64bb6917c0f6?filters=workflowStatus.Open%2CworkflowStatus.Pending&sort=lastUpdated:1 Uncaught (in promise) Object
bundle.80eb86a08fa84218a9df.js:93 – (action) clicked 2249edd4-6e52-4913-9f2e-6d4246befd94, selected record = Object
okapi-fse-eu-central-1.folio.ebsco.com/orders-storage/order-invoice-relns?limit=2147483647&query=purchaseOrderId%3D%3D2249edd4-6e52-4913-9f2e-6d4246befd94:1 Failed to load resource: the server responded with a status of 403 ()
/orders/view/2249edd4-6e52-4913-9f2e-6d4246befd94?filters=workflowStatus.Open%2CworkflowStatus.Pending&sort=lastUpdated:1 Uncaught (in promise) Object
18f95364-4123-41a9-9805-1b4a8cdc655d:1 PUT https://okapi-fse-eu-central-1.folio.ebsco.com/orders/order-lines/18f95364-4123-41a9-9805-1b4a8cdc655d 400
bundle.80eb86a08fa84218a9df.js:93 – (action) clicked "close edit"

Yesterday, we also saw "Access requires permission: orders-storage.order-invoice-relationships.collection.get" httpStatus: 403
I think it was when trying to perform the same as described above, but it could also have been when creating new POLs as described in

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

2

Checklist

hide

TestRail: Results

Activity

Show:

Marie Widigson February 27, 2020 at 6:27 PM

I just edited two of the examples (POLs 10161-1 and 10162-1) previously reported not being editable. Not sure if I succeded because this issue is now solved, or if something else has changed? (This is after having received a hotfix for MODORDERS-361).

Aliaksei Chumakou January 3, 2020 at 11:55 AM

could you please provide data you've used in your PUT request? Thanks. Without it I can't reproduce such error response

Dennis Bridges December 17, 2019 at 5:44 PM

I see thanks I will open one.

Theodor Tolstoy (One-Group.se) December 17, 2019 at 8:59 AM

There is something else lurking here. When you follow the guide, and only edit the Receiving note field, the backend replies that the details.productIds has changed:

I reran the PUT request in Postman, and even if you change nothing that error is thrown at you.

I mat a put request with the results of the GET request as well, but the same thing happened.Putting this back into the todo column, since I think we need to open a bug here.

Marie Widigson December 17, 2019 at 8:36 AM

Now I'm a bit confused, & There must be a misunderstanding.

We have been using the field Receiving note to enter information about for example delays, when the order is Open. This has been working, and is still working, for the majority of order records. See examples above.

Being able to add information about open orders is essential in the acquisition process.

Done

Details

Assignee

Reporter

Priority

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created December 11, 2019 at 4:57 PM
Updated February 27, 2020 at 6:28 PM
Resolved February 27, 2020 at 6:28 PM
TestRail: Cases
TestRail: Runs