Order field mapping: Vendor field error message

Description

Overview: For the Order field mapping profile's Vendor field, when an organization is selected from the Organization lookup, it populates into the field mapping profile without quotation marks, resulting in an error message
Current workaround: Manually insert quotation marks

Steps to Reproduce:
Case 1

  1. Log into FOLIO-snapshot-load as diku_admin

  2. Go to Settings/Data import/Field mapping profiles

  3. Start to create a new field mapping profile

    • FOLIO record type: Order

    • Vendor: Click "Organization lookup", search for GOBI, and select GOBI

    • View the data in the field mapping Vendor field

Case 2

  1. Log into FOLIO-snapshot-load as diku_admin

  2. Go to Settings/Data import/Field mapping profiles

  3. Start to create a new field mapping profile

    • FOLIO record type: Order

    • Vendor: type 980$a; else

    • Then click "Organization lookup", search for GOBI, and select GOBI

    • View the data in the field mapping Vendor field

Expected Results:

  • Case 1: Vendor field shows "GOBI Library Solutions"

  • Case 2: Vendor field shows 980$a; else "GOBI Library Solutions"

  • NOTE: The POL Material supplier and Access provider field mappings should work the same way

Actual Results:

  • Case 1: Vendor field shows GOBI Library Solutions

  • Case 2: Vendor field shows 980$a; else "GOBI Library Solutions", but only if you type in the vendor name; otherwise the vendor name wipes out all the other mapping data when you select it from the Organizations lookup

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 BreauxFebruary 27, 2023 at 5:20 PM

Hi Yes, all looks good, and I've edited the test case to make it clear that all scenarios are test-able now.

It looks like this was released in the Orchid main release, so I'm closing this Jira. Let me know if it needs to be Awaiting release instead. Thank you!

Maksym IshchenkoFebruary 24, 2023 at 10:56 AM

Hello  

This task verified on snapshot env. All looks good except the changing the fields not using reset "x" button. I create a bug for it (https://folio-org.atlassian.net/browse/UIDATIMP-1388) so please look on it. Except this little thing, all works properly, so i send task to In Review 

cc:  

Ann-Marie BreauxFebruary 21, 2023 at 8:35 AM
Edited

Hi I created TestRail https://foliotest.testrail.io/index.php?/cases/view/377020, and tested on Snapshot with 1) default mappings, 2) mapped codes, 3) mapped invalid codes. The last scenario would be the "else" scenario. I've written it into the Testrail, but cannot verify it until is merged. This one TestRail can be used for both Jiras.

Once is merged, and the 4th scenario of the TestRail works, then both Jiras can be closed, and the TestRail can be marked as Extended.

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Folijet

Fix versions

Release

Orchid (R1 2023)

RCA Group

Implementation coding issue

Affected releases

Orchid (R1 2023)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created February 2, 2023 at 8:10 AM
Updated March 15, 2023 at 6:22 AM
Resolved February 27, 2023 at 5:21 PM
TestRail: Cases
TestRail: Runs