Web Client: PO Activation Fails Silently if Line Items Linked to Deleted Bibs

Bug #1815238 reported by Jennifer Pringle
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Medium
Unassigned

Bug Description

Evergreen 3.1.7

When activating a purchase order it will hang indefinitely at 0% if one of the bibliographic records attached to a line item has been deleted.

In the xul client the error "EVENT 1128:BIB_RECORD_DELETED" was returned.

Ideally an error message should be returned in the web client so staff know what they need to fix in order to activate the purchase order

Revision history for this message
Tiffany Little (tslittle) wrote :

Related bug: https://bugs.launchpad.net/evergreen/+bug/1634244

Although that's interesting that you got that error message--I've also encountered this and never gotten the error message. +1 to having one, though.

Changed in evergreen:
status: New → Confirmed
Revision history for this message
Tiffany Little (tslittle) wrote :

My thought would be the easiest(?) thing would be to add a check in the PO activation for if eg_bib_id is deleted or is null, indicate which line item is affected. Then users can go undelete the record and try to activate again.

I'd include if it's null because we also have an issue where a line item didn't get linked to a bib, which also stops activation but doesn't *tell* them it's going to stop activation.

None of this would affect the Activate Without Loading Items.

tags: added: regression
Revision history for this message
Tiffany Little (tslittle) wrote :
tags: added: acq-lineitem acq-po
Revision history for this message
Andrea Neiman (aneiman) wrote (last edit ):

This is still occurring as of 3.11, in both Dojo and Angular PO interfaces. It gives the same user-visible-but-unhelpful error message as noted above in XUL, but it doesn't identify the bib(s) in question nor does it offer a path to resolution.

A workaround (ish) is that you can activate without loading copies, which doesn't of course solve the real problem.

Changed in evergreen:
importance: Undecided → Medium
Revision history for this message
Tiffany Little (tslittle) wrote :

ALSO not an actual fix, but my interim solution when someone runs into this is I have a report set up where you put in the PO name as the filter and it produces all the line items' eg_bib_id and whether or not the bib is deleted. Then users just go and undelete the offending bib and activation works fine.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.