...

• Inventory Item Import Error: ERROR [main] o.h.i.ExceptionMapperStandardImpl HHH000346: Error during managed flush [Validation failed for classes [org.ssdt_ohio.usas.inventory.model.AssetClass] during persist time for groups [javax.validation.groups.Default,]List of constraint violations:[ConstraintViolationImpl{interpolatedMessage='Code must be max 4 characters long.', propertyPath=code, rootBeanClass=class
  • This could be due to a wrapping issue on the ITEMS_EXP.TXT extract file caused by a hidden tab/space issue.  Please review the extract file in NOTEPAD++ to determine if each item is displayed on its on row starting at the left margin.  If you see wrapping similar to this (screenshot below), it's a very good indication there are hidden spaces/tabs in the data causing the formatting to wrap and resulting in error message above.  In the example, tags #001657, #001658 & #001659 are in the correct format, however you no longer see tags numbers line up to the left after that (red area).  The next tag #001660 should be listed at the left margin of row 1601.  Instead, it's still on row 1600 due to a possible hidden/tab space issue.  Please create a helpdesk ticket to SSDT attaching both the inventory import results file as well as the items extract file.

Image Added

Locations

• LocationCodeImportImpl: Warning: Location Number: CUMC has a blank category.
• LocationCodeImportImpl: Warning: Location Category: 001 has a blank number.
  
  • Missing part of the location:  The location code is made up of a location category and a location number.  The partial location will import in Core>Locations and any items containing the partial location will import as is in Transactions>Items. If you want to update the location codes, 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: You may use EISCHG>Mass Change Location Codes to mass change all items that contain the partial location code to a valid, complete location code.  When doing so, all items will be updated with the valid code and if the location is a new code, the location will be automatically added to EISMNT>LOCSCN.   
    • Fix in Redesign:  Using the Transaction>Items grid, extract the desired items with partial locations into an EXCEL spreadsheet.  Add the correct location_category or location_number and save the spreadsheet in CSV format. Use System>Import's Item Import type ensuring 'update records' is checked and import the updated locations.  If the location code is new and not currently in Core>Location, it will be automatically added when the spreadsheet is imported and the new location also noted on the import results report.  

...