Bug 33397 - Adding custom authorized values for bsort1/bsort2 can result in data loss
Summary: Adding custom authorized values for bsort1/bsort2 can result in data loss
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-04-03 19:25 UTC by Lucas Gass
Modified: 2023-08-10 16:04 UTC (History)
4 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lucas Gass 2023-04-03 19:25:17 UTC
To recreate:

1. Without having custom authorized values for bsort1/bsort2 create of edit some patrons with sort1 and sort2 values in their borrower information.
2. sort1/sort2 are free text fields
3. Create a new bsort1 and bsort2 authorized values. 
4. Go back to the patron record and notice the free text field is now a dropdown with the newly create authorized values.
5. Save the patron record without changing anything.
6. The initial values for sort1/sort2 are now empty.
Comment 1 Andrew Fuerste-Henry 2023-04-06 15:05:47 UTC
The same is somewhat true of the ASORT values for acquisitions, though with the added wrinkle that those authorised values aren't automatically linked to a field like the BSORT ones.