Details
-
Bug
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
None
-
None
-
-
EPAM-Veg Sprint 23, EPAM-Veg Sprint 24, EPAM-Veg Sprint 25, EPAM-Veg Sprint 26
-
2
-
Vega
Description
Overview:
When a duplicate term is entered in controlled vocab CRUD component in Settings, the addition fails with a weird server error. This applies in e.g. Settings > Inventory > Holdings, Holdings type, and Settings > Inventory > Instance, Holdings, Item > Call number type and more (basically everywhere this component is used in both Inventory and User settings.
This story will address fields outlined in the below bug. Additional stories will be created to address other fields.
Steps to Reproduce:
- Log into http://folio-snapshot.aws.indexdata.com as diku_admin
- Go to Settings > Inventory > Holdings, Holdings type, and Settings > Inventory > Instance, Holdings, Item > Call number type
- Create a new term with the same Name as an existing term
Expected Results:
The server will respond with the error code which will be handled on the UI
Actual Results:
The server responds with:
duplicate key value violates unique constraint "loan_type_name_idx_unique": Key (lower(f_unaccent(jsonb ->> 'name'::text)))=(can circulate) already exists.
TestRail: Results
Attachments
Issue Links
- has to be done after
-
MODINVSTOR-318 Disallow holdings types with same name
-
- Closed
-
- relates to
-
UXPROD-1838 Team Vega Q3 2019 Technical Debt
-
- Closed
-
- requires
-
STSMACOM-165 Controlled Vocab CRUD: When Record Name Isn't Unique, There Is No User Messaging (But Save Is Prevented)
-
- Closed
-