Acq: ORDERS messages created by EDIWriter not viewable in client
Bug #1785887 reported by
Chris Sharp
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Undecided
|
Unassigned | ||
3.2 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
PINES libraries report not being able to see ORDERS EDI messages attached to a purchase order in the staff client. In the example provided to us, three EDI messages are attached to the PO, one ORDERS and two ORDRSP. The client only counts two messages in the PO summary and only displays two, both ORDRSP, the EDI messages list view. Investigation shows that the "account" field on acq.edi_message was null, and the cause of that is the edi_order_pusher.pl script not setting that field as it creates the EDI message.
Evergreen 3.0+
OpenSRF 3.0.1
PostgreSQL 9.5
Ubuntu 16.04
Changed in evergreen: | |
milestone: | none → 3.1.5 |
assignee: | Bill Erickson (berick) → nobody |
status: | New → Confirmed |
Changed in evergreen: | |
milestone: | 3.1.5 → 3.1.6 |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix pushed:
http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ berick/ lp1785887- edi-order- pusher- sets-account
To test, I set up an edi_account with bogus connection data (server localhost, username foo, etc.) then ran edi_order_pusher.pl --po-id <id>. The script will ultimately fail trying to deliver, but not until after it's created the edi_message, which now contains an account value..