Summary: | Adding order from a staged file - "Some required subfields are unset" | ||
---|---|---|---|
Product: | Koha | Reporter: | Emily Lamancusa (emlam) <emily.lamancusa> |
Component: | Acquisitions | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | blawlor, caroline.cyr-la-rose, lucas, martin.renvoize, nick, sam.sowanick |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39294 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39282 |
||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: | ||
Attachments: | MARC record |
Description
Emily Lamancusa (emlam)
2024-12-19 20:33:46 UTC
I noticed that after that, the item type is still NULL and causes a whole slew of problems with the API later on. To recreate: 1. Go to Acquisitions 2. Click 'Search' under 'Search vendors' 3. Click 'Add to basket' next to 'My basket' 4. Click 'From a new file' 5. Choose a MARC file 6. Click 'Upload file' 7. Click 'Stage for import' 8. Click 'Add staged files to basket' 9. Click 'Default accounting details' 10. Select a fund 11. Click 'Item information' 12. Choose an item type in 'y - Koha item type' 13. Click 'Select to import' 14. Select the record 15. Enter a price 16. Click 'Save' 17. Click the title to access the bibliographic record --> API error If you look in the db, the itemtype is NULL MariaDB [koha_kohadev]> select itype from items where biblionumber = 439; +-------+ | itype | +-------+ | NULL | +-------+ 1 row in set (0.000 sec) 18. Go back to the basket 19. Click 'Close basket' 20. Click 'Yes, close (Y)' 21. Click 'Receive shipments' 22. Enter a vendor invoice number 23. Click 'Next' --> API error Created attachment 177703 [details]
MARC record
The MARC record I used to test. It has no item information in it.
Upping the severity to blocker since we can't do anything with items created this way, even if the user themself does everything right. I think Caroline's comments are bug 39282 - Emily is describing the need to set an item type when the items already have one, Caroline is encountering that when you do define item information in the second tab it isn't being used Given Nicks comment, I'm bringing this back down |