Migration Issue for TextBox Custom Fields (Fameflower-Goldenrod)

Description

Overview:
A tenant currently has 1 custom text field defined for users. This custom field was created while the tenant was running Fameflower version of FOLIO. The tenant was recently migrated to Goldenrod.

In Goldenrod, attempts to add a new User custom field or update a User to have a value for the existing custom field results in a 500 error.

When trying to add a new custom field – a null pointer exception is thrown in the log (attached)

Observed that existing custom field is missing fieldFormat attribute - and this is in the cause of NPE
"textField" : {
"fieldFormat" : "TEXT"
}

For this tenant we were able to work around this issue. We deleted and recreated the custom field (in Goldenrod) since it was not yet assigned to users.

Steps to Reproduce:

  1. Create a Text Box Custom field for Users in Fameflower environment

  2. Migrate a tenant from Fameflower to Goldenrod

  3. Try to add another custom field definition or update a user to have a value for this custom field

Expected Results:
Can add a new custom field and/or set a value for a user for the custom field
Actual Results:
Observe 500 error
Additional Information:

URL:
Interested parties:

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

2

Checklist

hide

TestRail: Results

Activity

Show:

Dima Tkachenko September 30, 2020 at 6:31 AM

Is there anything blocking this issue?

, don't see any

Carole Godfrey September 29, 2020 at 10:28 PM

I'm not aware of any blocking issue – probably can be closed

Khalilah Gambrell September 29, 2020 at 10:18 PM

, , and , we are not going to include this in a bug release. Is there anything blocking this issue?

Carole Godfrey September 28, 2020 at 3:08 PM

Dima Tkachenko September 25, 2020 at 8:52 AM
Edited


Please have a look at Pavel's comment above

So what do you think how serious this bug is?
Should we make a bug fix release? Keep in mind that Spitfire team doesn't release mod-users so it would need to be coordinated with Core functional team

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Spitfire

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created September 24, 2020 at 9:53 PM
Updated November 17, 2020 at 7:30 PM
Resolved September 30, 2020 at 3:28 PM
TestRail: Cases
TestRail: Runs