Data Import field mapping profile is saved with data deleted from the system

Description

Overview: The user can save a mapping profile with data that has been deleted from the system.

Precondition: The user is authorized with  "Settings (Data import): Can view, create, edit, and remove" and "Settings (acquisition units): Can view, edit, create and delete acquisition units" permissions.

Steps to Reproduce:

  1. Go to Settings->Acquisitions units

  2. Create the value for the Acquisitions unit

  3. Go to Settings >Data import>Field mapping profile

  4. Click the invoice mapping profile from the list 

  5. Click the Actions > Duplicate 

  6. Change the value in the Name field 

  7. Click on the 'Accepted values' button in the 'Acquisitions units' field.

  8. Select the value, that you created in step 2

  9. In a separate window, go back to the Acquisitions unit settings, and delete the value in that you created in step 2

  10. Go back to the Data import duplicate mapping profile and  fill in all other required fields

  11. Click the "Save as profile & Close" button

Expected Results

  • The mapping profile cannot be saved because the 'Acquisitions units' field contains data that has been deleted.

  • Error message is displayed for a field that contains invalid data.

Actual Results: The mapping profile was saved with the data in the fields that were deleted from the system.

Additional Information: See attached video 

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

1

Checklist

hide

TestRail: Results

Activity

Show:

Ann-Marie BreauxMay 22, 2023 at 6:42 PM

Hi I agree it's an edge case, and have moved to P4. Not exactly optimistic locking, since we're only dealing with one version of the field mapping profile record being edited, not 2. I think what would resolve it is re-checking the reference values when the user presses save, then disallowing save/showing error if any selected reference value has been deleted from settings.

Khalilah GambrellMay 22, 2023 at 12:16 PM

  - this seems to be an edge case and could be resolved by optimistic locking. 

Ann-Marie BreauxJanuary 18, 2023 at 3:37 PM

Per to resolve this would require additional validation in profiles, Some Jiras are linked to this one. Review with , and determine if we can take care of all of these in Poppy (probably not in Orchid). Has not been reported by production tenants, so leaving as P3 for now

Ann-Marie BreauxAugust 23, 2022 at 4:53 AM

Hi Good catch!

This is an odd little problem, but it definitely reproduces. I'm not sure how it should be resolved, but we definitely need to end up with a field mapping profile that can be saved, or some sort of error message that associate reference data has been changed, so the user needs to start over.

Since I don't think this will occur frequently, I'm marking it as P3 and Nolana

Won't Do

Details

Assignee

Reporter

Priority

Development Team

Folijet

Release

Not Scheduled

RCA Group

Lack of testing

Affected releases

Orchid (R1 2023)
Nolana (R3 2022)
Morning Glory (R2 2022)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created August 19, 2022 at 11:49 AM
Updated May 14, 2024 at 3:05 PM
Resolved May 14, 2024 at 3:05 PM
TestRail: Cases
TestRail: Runs