Done
Details
Assignee
Mikhail FokanovMikhail FokanovReporter
Kyle BanerjeeKyle BanerjeeLabels
Priority
P1Sprint
NoneDevelopment Team
Core: PlatformFix versions
Release
R1 2021 Hot FIx #2CSP Approved
YesAffected Institution
5 CollegesBNCFChalmersCornellDukeGBVLehighMI State University/Library of MichiganMO StateOTHERSHLSimmonsSpokane Public LibrariesSt. Michael's CollegeSTUTAMUUniversity of AlabamaUniversity of ChicagoUniversity of LeipzigUniversity of Tennessee MartinWarnerWashington-JeffersonTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Mikhail Fokanov
Mikhail FokanovReporter
Kyle Banerjee
Kyle BanerjeeLabels
Priority
Sprint
None
Development Team
Core: Platform
Fix versions
Release
R1 2021 Hot FIx #2
CSP Approved
Yes
Affected Institution
5 Colleges
BNCF
Chalmers
Cornell
Duke
GBV
Lehigh
MI State University/Library of Michigan
MO State
OTHER
SHL
Simmons
Spokane Public Libraries
St. Michael's College
STU
TAMU
University of Alabama
University of Chicago
University of Leipzig
University of Tennessee Martin
Warner
Washington-Jefferson
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created June 8, 2021 at 6:35 PM
Updated June 28, 2021 at 4:29 PM
Resolved June 25, 2021 at 12:09 PM
Purpose/Overview:
Initially reported by Skidmore, verified in Skidmore and bugfest – suspect it affects many institutions.
After a patron record has been modified in the UI (any field tested), any subsequent attempts to update that record in a bulk load results in the error:
Desired functionality:
Bulk loaded values are preferred and overwrite existing values for which fields are preferred
To replicate:
Add user group Alumni.
Modify any value for the user and correct via API and it updates properly provided data constraints are followed.
Modify any value for the user via the GUI (add a single character to the last name, add a preferred name, etc), and then the record can no longer be updated via API