Versions Compared

Version Old Version 25 New Version 26
Changes made by

Michelle Drewes

Michelle Drewes

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • DispositionImportImpl: Warning: Invalid Disposition Code: for Item #: xxxxxx
    • Missing Disposition Method: The disposition transaction will import with the missing or invalid disposition method.  If you want to update the disposition method, you may fix it in Classic prior to extract or wait until the data has been migrated to fix it in Redesign using one of the steps provided below. 
      • Fix in Classic: Please review the tag in EISSCN>DSPTRN and update it by adding a disposition method. 
      • Fix in Redesign: Using the Transaction>Dispositions grid, extract the desired dispositions into an EXCEL spreadsheet.  Add the correct disposition code and save the spreadsheet in CSV format. Use System>Import's Dispositions Import type ensuring 'update records' is checked and import the updated disposition transactions.  If the disposition code is new and not currently in Core>Dispositions, it will be automatically added when the spreadsheet is imported and the new disposition also noted on the import results report.  

Items:

  • Inventory Item Import Error: Duplicate Tag Number found on row: xxxx

    17:29:46.193 ERROR [ main] o.h.engine.jdbc.spi.SqlExceptionHelper   ERROR: duplicate key value violates unique constraint "uk_inventoryitem_tagnumber" Detail: Key (tagnumber)=(11202) already exists.

    17:29:46.195 ERROR [  main] o.h.i.ExceptionMapperStandardImpl        HHH000346: Error during managed flush [org.hibernate.exception.ConstraintViolationException: could not execute statement]

    • Duplicate tag on file: This could be possible if one of the tag numbers includes a blank space as part of the number.   The one with the blank space will import first (the importer drops the space) thus resulting in the duplicate number to not import.
      • Fix in Classic: If it is a true duplicate, the district needs to delete the duplicate tag in EISSCN>ITMSCN.  If it's not a duplicate, they need to change the tag number with the blank space in EISSCN>ITMSCN in order to allow both tags to import.

...