Load MARC Order Records screen Fiscal Year field only accepts current year.
Bug #2021992 reported by
Dale Rigney
This bug affects 9 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
High
|
Unassigned |
Bug Description
Tested on 3.10.
The new angular Load MARC Order Records screen only accepts the current year (2023) in the Fiscal Year field. This causes item import issues when the fund for the item is not a 2023 fund. If your library has a active funds from the previous year your Evergreen will give you an ACQ_IMPORT_ERROR (no funds with code xxxx at orgs [xxx] error message.
The legacy screens will allow you to choose this year as well as past years.
tags: | added: acq acq-loadmarc |
Changed in evergreen: | |
status: | New → Confirmed |
importance: | Undecided → High |
To post a comment you must log in.
The Fiscal Year selector in the Load MARC Order Records appears to be a drop down selection list, but it does not link to any ACQ fund related fiscal year data, presumably drawing from the OU setting Fiscal Year field, which is (apparently) configured in the database?
This is a massive issue for libraries with non-calendar year fiscal years.
We have libraries that FYs ending in May and July, where the FY is will be out of sync with the current year default for half the year.
See also bugs https:/ /bugs.launchpad .net/evergreen/ +bug/1486213 and https:/ /bugs.launchpad .net/evergreen/ +bug/1962622, related to managing fiscal year configurations and non-calendar year FYs support.