[UXPROD-3837] Add RefId value to the display of a custom field in Settings > Users Created: 06/Oct/22 Updated: 30/Nov/23 |
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Erin Nettifee | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | enettifee-reviewed, ui-only | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue links: |
|
||||||||
| Development Team: | Volaris | ||||||||
| PO Rank: | 0 | ||||||||
| Rank: Cornell (Full Sum 2021): | R3 | ||||||||
| Description |
|
When creating a custom field, FOLIO creates a reference ID for that field based off of the provided field name. It would be really helpful to implementers if the reference ID could be displayed in the user interface - it would help with understanding the behavior of the underlying data. Example: results in a custom field with a refId of "studentAcademicProgram", as seen here using developer tools to view the underlying data. That value is what we want to display somewhere on this view, in a read-only format (since it cannot be changed once the field is created.) Questions to be answered:
|
| Comments |
| Comment by Erin Nettifee [ 06/Oct/22 ] |
|
Theodor Tolstoy (One-Group.se) here is the feature for adding refId that I started, please feel free to add more / modify what I wrote. Khalilah Gambrell I went ahead and put Spitfire on as the dev team, but if that's wrong, let me know (or feel free to just change it obviously.) |
| Comment by Erin Nettifee [ 06/Oct/22 ] |
|
patty.wanninger related to UM |
| Comment by Theodor Tolstoy (One-Group.se) [ 06/Oct/22 ] |
|
Thank you Erin Nettifee . Looks good! My answer to your first question is that this is sufficient. |
| Comment by Erin Nettifee [ 06/Oct/22 ] |
|
Gotcha Theodor Tolstoy (One-Group.se) - I'll label this as ui-only then, since all we're doing is exposing a field in the UI that already exists in the data. |