Data Import Log Error Messages
- Jennifer Eustis
Inventory single record import Error Messages
Inventory single record imports sometimes aren’t able to complete. These will show only in the View all logs with the status of “Completed with errors”.
To get to the detailed view, click on the file name. In the Summary, the number of error(s) will be one because this is an Inventory single record import.
From the detailed view, if you click on the title to view the JSON, the record type that has the error is marked with an asterisk. This is where a short error message can be found in the red box just under the Import Log Record title.
Unfortunately, these JSON short error messages are sometimes obscure. It is recommended with Inventory single record import to contact your systems team and/or hosting provider.
Error Messages for Other Imports
Once you click on the File name to get to the summary and title list, click on the Error(s) in the Summary at the top or sort the column Error to have those titles with errors appear at the top of the list.
Click on the title which has the error to get to the JSON view. Find the record type with the asterisk and click on that tab.
In this example, the error is related to the Item Material Type which isn’t correct in the incoming file and hence this wasn’t able to be mapped to the Item record being created. Because item material type is a required field, the creation of this particular item record failed.
Troubleshooting
In the case above, how would it be possible to find out what happened and fix it? First find the error in the JSON view and read through it. If it is something that you can read like the material type is missing, then in this case it is worth looking at the file you imported. If there is no material type, then make a note to ensure that this data is present when you do a similar import. In FOLIO, you can go to the holdings record and manually create the item record.
Not All Log Messages Make Sense
Sometimes, there will just be a message of “No Content” or “No Record”. Other log messages don’t make sense like the one shared above for the Inventory single record import where the error said there were duplicates for 1 record. If you need understanding a JSON error message, reach out to your systems coordinators, the Data Import Lab Session Slack channel, and/or your hosting providers.
Full JSON error message:
io.vertx.core.impl.NoStackTraceThrowable: [{"id":"b2fd15c8-f749-4a54-8c07-49d52b70440b","error":"Mapped Item is invalid: [Field 'materialType.id' is a required field and can not be null], by jobExecutionId: 'bd32aaeb-4bc0-47ee-9eaa-da8700edcb2f' and recordId: '8413824a-a2ee-4c14-a897-5562e3ee7382' and chunkId: '8384c819-41ae-4f2a-b035-74df676d7336' ","holdingId":"d5b27bba-e98a-4266-a464-101866631fd9"},{"id":"8eee307a-8c47-4a3d-86b2-0ed53b93bdab","error":"Mapped Item is invalid: [Field 'materialType.id' is a required field and can not be null], by jobExecutionId: 'bd32aaeb-4bc0-47ee-9eaa-da8700edcb2f' and recordId: '8413824a-a2ee-4c14-a897-5562e3ee7382' and chunkId: '8384c819-41ae-4f2a-b035-74df676d7336' ","holdingId":"fd6d55af-1faf-49da-afc2-e7df78f2c063"},{"id":"33e5dc03-2567-48f9-8eb4-df3faf99d360","error":"Mapped Item is invalid: [Field 'materialType.id' is a required field and can not be null], by jobExecutionId: 'bd32aaeb-4bc0-47ee-9eaa-da8700edcb2f' and recordId: '8413824a-a2ee-4c14-a897-5562e3ee7382' and chunkId: '8384c819-41ae-4f2a-b035-74df676d7336' ","holdingId":"7bd00b43-0416-4f17-bd06-7c61348f07c4"},{"id":"61cb24d6-2b94-48b6-8a2d-bca76de84fd8","error":"Mapped Item is invalid: [Field 'materialType.id' is a required field and can not be null], by jobExecutionId: 'bd32aaeb-4bc0-47ee-9eaa-da8700edcb2f' and recordId: '8413824a-a2ee-4c14-a897-5562e3ee7382' and chunkId: '8384c819-41ae-4f2a-b035-74df676d7336' ","holdingId":"f83e46e9-1038-40be-bffb-b2091ef1c4f9"},{"id":"fab0e400-019d-4b6d-90d2-bf74c9a2b7e1","error":"Mapped Item is invalid: [Field 'materialType.id' is a required field and can not be null], by jobExecutionId: 'bd32aaeb-4bc0-47ee-9eaa-da8700edcb2f' and recordId: '8413824a-a2ee-4c14-a897-5562e3ee7382' and chunkId: '8384c819-41ae-4f2a-b035-74df676d7336' ","holdingId":"259bf0b8-e9cc-4119-90c2-d02192897058"}]