New Brief Record estimated price does not populate

Bug #1413352 reported by Leslie St. John on 2015-01-21
This bug affects 2 people
Affects Status Importance Assigned to Milestone

Bug Description

The estimated price in a new brief record does not populate the selection list although the brief record created contains the price that was input. Two 020's are created, one with a subfield a for ISBN and another with a subfield c containing the price. Probably two 020's is not the reason for the bug but may be a clue? The estimated price should populate the selection list.

ver 2.7.1

tags: added: acq
Chris Sharp (chrissharp123) wrote :

Steps I took to reproduce this:

1) Navigated to Acquisitions -> New Brief Record

2) Selected an existing Selection List and filled most of the form fields, including price, but omitting ISSN, UPC, and Publisher Number.

3) Clicked Save Record.

I was brought to my test selection list with the new record in place, but without the Price field populated. I can verify that the price was not created in the acq.lineitem row in the database, too (see attached).

Changed in evergreen:
status: New → Confirmed
importance: Undecided → High
Martha Crawley (mcrawley) wrote :

We don't use selection lists, but when we create a new brief record from within a PO, I think the price you enter in the record should populate the price field on the PO but it doesn't.

Bill Erickson (berick) on 2016-06-02
Changed in evergreen:
assignee: nobody → Bill Erickson (berick)
Bill Erickson (berick) wrote :

Fix pushed:;a=shortlog;h=refs/heads/user/berick/lp1413352-acq-li-brief-record-price

In summary:

The code propagates the lineitem MARC 'price' attribute value to the lineitem estimated_unit_price field during lineitem creation, if no estimated_unit_price is already applied. This allows users to apply a lineitem price directly from the ACQ Brief Record interface.

tags: added: pullrequest
Changed in evergreen:
milestone: none → 2.10.5
assignee: Bill Erickson (berick) → nobody
Changed in evergreen:
milestone: 2.10.5 → 2.10.6
Changed in evergreen:
milestone: 2.10.6 → 2.10.7
Mike Rylander (mrylander) wrote :

Thanks, Bill. Merged to master and back branches.

Changed in evergreen:
status: Confirmed → Fix Committed
Changed in evergreen:
status: Fix Committed → Won't Fix
status: Won't Fix → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers