Uploaded image for project: 'mod-data-import'
  1. mod-data-import

EDIFACT files with CAPS file extensions do not import



    • 0.5
    • Folijet Support
    • R2 2021 Bugfix


      Overview: When an invoice file has a CAPS file extension of INV or EDI, you can upload it, but cannot import it. It fails silently, with no error or indication of what happened. If the EDIFACT invoice file has an extension of lower-case inv or edi, you can upload it and import it. MARC files with upper-case, lower-case, or mixed-case file extensions import just fine.

      Current workaround: Change the invoice file extension to lower case before uploading the file (added this note to the Iris release notes)

      Steps to Reproduce:

      1. Log into FOLIO-snapshot-load as diku_admin
      2. Go to Settings/Data Import/Field mapping profile
      3. Find the Default EBSCO Serials Invoice field mapping profile
      4. Go to Actions/Duplicate
      5. Update the new field mapping profile as follows (leave the existing mapping info unless change or addition described below)
        • Name: Import EBSCO Serials Invoice
        • Description: Delete all the existing text
        • Batch group: "FOLIO"
        • Vendor name: use the vendor lookup to find and select EBSCO
        • Payment method: "EFT"
        • Currency: Delete existing info and select "USD" from the dropdown menu
        • Vendor reference number: leave the existing one for RFF+SNA, and add another one
          • Vendor reference number: RFF+LI[2]
          • Vendor reference type: "Vendor subscription reference number"
        • Save the updated profile
      6. Go to Action profiles and create a new profile
        • Name: Create EBSCO subscription invoice
        • Action: Create
        • FOLIO record type: Invoice
        • Link the field mapping profile to it and save
      7. Go to Job profiles and create a new profile
        • Name: Create EBSCO Subscription Invoice
        • Accepted data type: EDIFACT
        • Click + and select Action
        • Find the action profile you just created and attach to the job profile
      8. Now you have an EDIFACT invoice job profile
      9. Go to Data import and upload the attached file that has a file extension of ".inv" (lower-case
      10. In the Select job profile screen, select the EBSCO invoice job profile and run it
      11. Once the import completes (and displays at the top of the landing page list), upload the attached file that has a file extension of ".INV" (upper-case)
      12. In the Select job profile screen, select the EBSCO invoice job profile and run it

      Expected Results: Both files should import successfully. The case of a file extension (all-upper-case, all-lower-case, or mixed case) should not matter.

      Actual Results: The file with ".inv" imports successfully. The file with ".INV" does not import and seems to just disappear. For comparison, import the attached ".mrc", ".mrC" and ".MRC" files with the Default create instance and SRS MARC Bib job profile. All 3 MARC files import successfully.

      Additional Information: See attached video and files

      TestRail: Results


          1. EDIFACT file extension problem, part 1.mp4
            13.35 MB
            Ann-Marie Breaux
          2. EDIFACT file extension problem, part 2.mp4
            9.55 MB
            Ann-Marie Breaux
          3. image-2021-07-30-14-53-26-528.png
            218 kB
            Yevheniia Panchenko
          4. recordsa.mrc
            2 kB
            Ann-Marie Breaux
          5. recordsb.MRC
            2 kB
            Ann-Marie Breaux
          6. recordsc.mrC
            0.5 kB
            Ann-Marie Breaux
          7. SC SUMMARY AND LINE HLI KOH0002.R031820.T165006.inv
            8 kB
            Ann-Marie Breaux
          8. SC SUMMARY AND LINE HLI KOH0002.R031820.T165006a.INV
            8 kB
            Ann-Marie Breaux

          Issue Links



                bisecomsergiy Sergiy Bichurin
                abreaux Ann-Marie Breaux
                0 Vote for this issue
                5 Start watching this issue



                  TestRail: Runs

                    TestRail: Cases