Issues
- Make custom field refId value settableMODCFIELDS-71
- Remove regular expression validation from custom field option valuesMODCFIELDS-70
- Upgrade Spring, RMB, folio-di-support (CVE-2022-22965)MODCFIELDS-69Resolved issue: MODCFIELDS-69Julian Ladisch
- Locale independent unit testsMODCFIELDS-68Resolved issue: MODCFIELDS-68Julian Ladisch
- Incorrect multiselect options usage stats returned from back-endMODCFIELDS-62Resolved issue: MODCFIELDS-62Pavlo Smahin
- Support Custom Fields Search - Phase 1MODCFIELDS-60Resolved issue: MODCFIELDS-60
- Release mod-custom-fields v1.4.1MODCFIELDS-59Resolved issue: MODCFIELDS-59Natalia Zaitseva
- Incorrect order of Custom Fields when drag-n-drop fieldsMODCFIELDS-57Resolved issue: MODCFIELDS-57Natalia Zaitseva
- Use camel-case names for auto-generated refIds, only use counter value if neededMODCFIELDS-56Resolved issue: MODCFIELDS-56Pavlo Smahin
- Incorrect order of Custom Fields when adding a 10th fieldMODCFIELDS-55Resolved issue: MODCFIELDS-55Natalia Zaitseva
- Custom fields: Add restriction for applicationMODCFIELDS-54Resolved issue: MODCFIELDS-54
- Rename mod-custom-fieldsMODCFIELDS-53Resolved issue: MODCFIELDS-53Pavlo Smahin
- mod-custom-fields: Update to RMB v30MODCFIELDS-49Resolved issue: MODCFIELDS-49Pavlo Smahin
- MODCFIELDS (mod-custom-fields) releaseMODCFIELDS-47Resolved issue: MODCFIELDS-47Pavlo Smahin
- Custom Field Option: Provide an indication that an option has been saved to a recordMODCFIELDS-46Resolved issue: MODCFIELDS-46Pavlo Smahin
- Input type | Radio button | Options | Add a code fieldMODCFIELDS-45Resolved issue: MODCFIELDS-45
- Input type | Single select | Options | Add a code fieldMODCFIELDS-44Resolved issue: MODCFIELDS-44
- Create an unique identifier for each optionMODCFIELDS-43Resolved issue: MODCFIELDS-43Pavlo Smahin
- Create MODCFIELDS releaseMODCFIELDS-41Resolved issue: MODCFIELDS-41Dima Tkachenko
- Make RefId a read-only fieldMODCFIELDS-40Resolved issue: MODCFIELDS-40Dima Tkachenko
- Prepare for Custom Field backend demoMODCFIELDS-39Resolved issue: MODCFIELDS-39Natalia Zaitseva
- Security update jackson-databind >= 2.9.10.1MODCFIELDS-38Resolved issue: MODCFIELDS-38Pavlo Smahin
- Custom Field: Repeatable field supportMODCFIELDS-37Resolved issue: MODCFIELDS-37Pavlo Smahin
- Text field can be created without requried "textField" attributeMODCFIELDS-36Resolved issue: MODCFIELDS-36Pavlo Smahin
- User Record | Import Custom Field | Update user import schema when field and values does not exist in SettingsMODCFIELDS-35Resolved issue: MODCFIELDS-35Pavlo Smahin
- Custom Fields: Support delete by refIdMODCFIELDS-34Resolved issue: MODCFIELDS-34
- Custom Fields: Support update by refIdMODCFIELDS-33Resolved issue: MODCFIELDS-33
- Custom Fields: Support search by refId GET /custom-fields/{id}MODCFIELDS-32Resolved issue: MODCFIELDS-32
- Update versions in schema.json according to rules for DB migrationMODCFIELDS-30Resolved issue: MODCFIELDS-30Andrii Paias
- Upgrade to RMB v29.xMODCFIELDS-29Resolved issue: MODCFIELDS-29Dima Tkachenko
- Create MODCFIELDS releaseMODCFIELDS-28Resolved issue: MODCFIELDS-28Dima Tkachenko
- Custom Fields: Support fields order on PUT /custom-fieldsMODCFIELDS-27Resolved issue: MODCFIELDS-27Andrii Paias
- Custom Fields: Support fields order on DELETE /custom-fields{id}MODCFIELDS-26Resolved issue: MODCFIELDS-26Natalia Zaitseva
- Custom Fields: Support fields order on POST /custom-fieldsMODCFIELDS-25Resolved issue: MODCFIELDS-25Natalia Zaitseva
- Normalize custom field content according to its type during creation and updatingMODCFIELDS-24Resolved issue: MODCFIELDS-24Andrii Paias
- Custom Fields: Dropdown,Checkbox,Radiobutton Values ValidationMODCFIELDS-22Resolved issue: MODCFIELDS-22Andrii Paias
- [Spike] Getting familiar with User Data import to see how it can import custom fieldsMODCFIELDS-21Resolved issue: MODCFIELDS-21Andrii Paias
- Upgrade RMB to 27.1.1MODCFIELDS-20Resolved issue: MODCFIELDS-20Natalia Zaitseva
- Custom Fields: Checkbox Values ValidationMODCFIELDS-19Resolved issue: MODCFIELDS-19
- Support custom field usage statisticMODCFIELDS-18Resolved issue: MODCFIELDS-18Dima Tkachenko
- Custom Fields: Radio Button Definition ValidationMODCFIELDS-17Resolved issue: MODCFIELDS-17Natalia Zaitseva
- Custom Fields: Dropdown Definition ValidationMODCFIELDS-16Resolved issue: MODCFIELDS-16Natalia Zaitseva
- Custom Fields: Text field/area Values ValidationMODCFIELDS-15Resolved issue: MODCFIELDS-15Andrii Paias
- Spike: Custom fields validationMODCFIELDS-14Resolved issue: MODCFIELDS-14Natalia Zaitseva
- Custom fields: Common fields Definition ValidationMODCFIELDS-13Resolved issue: MODCFIELDS-13Natalia Zaitseva
- Document X-Okapi-Module-Id multiple interfaces requirementMODCFIELDS-12Resolved issue: MODCFIELDS-12Natalia Zaitseva
- Update CF Definition schema to separate type specific dataMODCFIELDS-11Resolved issue: MODCFIELDS-11Natalia Zaitseva
- Move common test code to folio-service-tools moduleMODCFIELDS-9Resolved issue: MODCFIELDS-9Andrii Paias
- User Record | Import Custom Field | Update user import schema when field and values exist in SettingsMODCFIELDS-10Resolved issue: MODCFIELDS-10Pavlo Smahin
- Implement DELETE custom field by id endpointMODCFIELDS-8Resolved issue: MODCFIELDS-8Natalia Zaitseva
50 of 58
The refId value in a custom field appears to be generated based on the name field of the custom field. Can you make this value settable?
Currently, the code is assigning a digit value to the end of the field. If you add, remove, and re-add a field, it appears that the digit can change. The reason it's important is because the refId value is the name of the JSON property in whatever object you are working with. For example, a user object.
There may be other applications that make use of the field. Therefore it is important to be able to control what the field is named. It may also appear in the reports database under that name. So, it is not ideal to have FOLIO assigning the value in an uncontrolled manner.