Uploaded image for project: 'ui-data-import'
  1. ui-data-import
  2. UIDATIMP-1008

Invoice field mapping profile only displays first 10 acq unit values

    XMLWordPrintable

    Details

    • Template:
      Folijet UI bug template
    • Story Points:
      0.5
    • Development Team:
      Folijet
    • Release:
      R3 2021

      Description

      Overview: If there are more than 10 acquisitions units for a tenant, the invoice field mapping profile only shows the first 10 in the dropdown list

      Current workaround: None

      Steps to Reproduce:

      1. Log into FOLIO-snapshot-load as diku_admin
      2. Go to Settings/Acquisitions Units
      3. Create 12 Acquisitions units (New, Assign a name, Save). Make sure there are more than 10 Acquisitions Units in the list
      4. Go to Settings/Data Import/Field Mapping profiles
      5. Click Actions/New and begin creating a field mapping profile for an invoice
      6. Find the field for Acquisitions unit and click the dropdown list
      7. Count the number of values in the list

      Expected Results: All values should display , in alphabetical order

      Actual Results: Only the first 10 values display, and they are not in alpha order
      NOTE There's also bug UIAC-37 assigned to Thunderjet, which will fix the alpha order in the Acq Unit settings. I'm not sure if that will fix the sequence in the Data Import dropdown list also, or if Folijet needs to fix it separately on the field mapping profile

      Additional Information: See attached screenshots

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Ivan Kryzhanovskyi Ivan Kryzhanovskyi
                Reporter:
                abreaux Ann-Marie Breaux
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases