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

Invoice Field Mapping profile: Acq unit and Batch group dropdown lists should be in alphabetical order

    XMLWordPrintable

Details

    • 1
    • Folijet Support
    • Nolana (R3 2022)
    • Implementation coding issue

    Description

      Overview: The 'Accepted values' dropdown lists for Acquisitions unit and Batch group are not in alphabetical order in the Invoice field mapping profile. All dropdown lists in field mapping profiles should be in alphabetical order unless otherwise specified

      Precondition: There are more than 20 Acquisitions units in Settings/Acquisitions units, and more than 20 Batch groups in Settings/Invoices/Vouchers/Batch groups. When creating them, mix upper-case and lower-case, and DO NOT create them in alphabetical or numerical order.

      Steps to Reproduce:

      1. Log into the application.
      2. Go to Settings -> Data import -> Field mapping profiles
      3. Click on Actions/New
      4. For FOLIO record type, select Invoice
      5. Go to the Acquisitions units field and click on the dropdown list. Review the sequence of the values in the list
      6. Go to the Batch group field and click on the dropdown list. Review the sequence of the values in the list

      Expected Results: The dropdown lists for Acquisitions units and Batch group are in alphabetical order, with upper-case and lower-case in one intermingled sequence.

      Actual Results: The dropdown list values display in the order in which they were manually created in the Acq unit or Invoices/Batch group settings. (In those settings though, they display in the correct order, not matter what order they were created in.)

      Additional Information: See attached videos

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                javokhir12 Javokhir Rajabboev
                abreaux Ann-Marie Breaux
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases