How to Fix Load File Errors

Fix common load file errors with these tips

John OHara avatar
Written by John OHara
Updated over a week ago

⚠️ If a load file errors, it is always best practice to request a new, corrected load file from the producing party, as making changes to your load file may affect the original metadata. The remediations below are meant as a last resort if you are not able to receive new load files.

There are a number of common errors you may encounter when you are completing production uploads. πŸ”—
Some of these errors can be easily fixed using free tools as well as a simple find-and-replace function in a text editor program.

Tools needed

Free text editors:
Windows: Notepad ++ πŸ”—
Mac: BBEdit πŸ”— (also free for download in the App Store)
​Spreadsheet tools:
Microsoft Excel or Google Sheets (free)

Parsing Errors

The metadata loadfile could not be parsed

This error will usually appear before you get to the mapping screen. This error may be caused by unsupported encoding of your load file. If this is the case, you can attempt to change the encoding of your load file to UTF-8 using the steps below.


  1. Open your load file in your free text editor, like BBEdit or Notepad++

  2. Click File > Save As

  3. Change the encoding from whatever it's set as to UTF-8

  4. Save the new load file as a new copy of the original load file. I like to put _MOD in the name. Make sure the encoding is set to UTF-8 and save

  5. Use the new _MOD load file in the place of your old load file on step 2 of the production upload.

Change Encoding Video

Date/Time Errors

A common error that occurs after mapping validation is Date/Time errors which look like this:

Date/Time errors occurs when the values if the Date or Time fields do not confirm to our accepted Date/Time formats. Acceptable Date/Time formats are outlined in our production upload requirement article πŸ”—
Our accepted formats are:













hh:mm:ss [AM|PM]
hh:mm [AM|PM]

h:mm [AM|PM]

h:mm:ss [AM|PM]



12/31/2019 1:13:30 PM
12/31/2019 1:13 PM
12/31/2019 1 13 30 PM
12/31/2019 1 13 PM
12-31-2019 1:30 PM
12-31-2019 13:13:30
12-31-2019 13:13
2019-12-31 13:13:30
2019-12-31 13:13
20191231 131330
20191231 1313

Months (mm), days (dd), and hours (hh) may all be denoted by a single digit except for yyyy-mm-dd and yyyymmdd formatting.
If the time is in military format, the AM/PM indicator is not required.

Fixing Date/Time Errors

Converting a DAT into a CSV

1. Open your DAT in your text editor.
2. Open the find and replace box:

3. As quotation marks are one of the CSV delimiters, escape any existing quotes by prepending an additional quotation mark:

Replace " with "":

4. Next replace the column breaks with β€œ,”. In most standard DATs these are ΓΎ and upside down question mark (as a non printable character, we can reference this with the following hex value: \x{14}m ).

Replace ΓΎ\x{14}ΓΎ with ","

5. The ΓΎ at the beginning and end of each line will be replaced with a quotation mark.

Replace ΓΎ with "

6. The result should look something like this:

7. Save As the DAT and change the extension to CSV. Add MOD in the name so you know this is modified load file you made. Make sure the encoding is UTF-8:

DAT to CSV Conversion Video

Once the DAT has been converted into a CSV, you can open it in excel to convert the dates/times into Logikcull accepted formats.

Converting Date/Times in Excel


1. Select the date or time column(s) that need to formatted:

2. Right click on one of the values in a cell and click format cells:

3. In the pop up window, select custom and choose the appropriate Logikcull supported Date/Time formatting:

4. Once the all dates/times have been updated, save the CSV as _MOD.

You can now use this in place of your original DAT in step 2 of the Production Upload by clicking "Re-Upload Load Files".

IMPORTANT: Do NOT open the modified CSV before you re-upload into Logikcull. If you open the file, the date/time changes will revert to the unsupported formats.

Missing Images, Natives, or Text Errors

Another common error missing text, native, and image file errors. Typically these are caused by the path in your zip not matching the path referenced in your load files. You can confirm the actual files aren't missing by looking in your volume zip and checking for a sample image, native, and text.
The error looks like this:

And the error report will typically read like this:
​(warning) Line 2: Missing text file for TESTIMPORT0001: Test Import\Top Level\TEXT\TESTIMPORT0001.txt
​(warning) Line 4: Missing native file for TESTIMPORT0003: Test Import\Top Level\NativeFiles\TESTIMPORT0003.doc
These error will give you the option to skip and continue with the upload; however we recommend you do not skip them if the files exist in your volume zip. This error can usually be solved with a find and replace. Removing everything in the path before the top level NATIVE, TEXT, and IMAGE folders and making the paths relative is usually the solution to these errors.

Resolving Missing Native, Text, and Image Errors


1. Open up your DAT and your OPT in a text editor
2. Control + F and search for Native and jump to the first native path; Copy the first part of the path to the natives folder and then do a find and replace all like so:

The resulting path should look something like this, with all the leading folders before the native folder removed:

So if the original path was VOL001\NativeFiles\BATES00000013.ics, after the find and replace, the path should be \NativesFolder\BATES00000013.ics. The leading \ before the natives, text, and images folders is still needed.

Note, your native folder may be called NATIVES so your replacements and resulting native path may differ.
3. Repeat this for the Text and Image paths:

4. Save As the modified load files as new load files (do NOT save over your old load files):

Fixing Native, Text, and Image Path Video

The new, modified load files can now be used in the place of out old load files. If you have already zipped up your volume, you do not need to remove the old load files from the zip and you do not need to add the new load files to the zip. You will simply need to replace the load files by clicking the "Re-upload load files" button:

Other Common Metadata Load File Errors

  • Document is contained in its own attachment range. If your "Begin Attach" field contains parent IDs, please map to "Begin Family"

    • The error is pretty self explanatory. The fix is to go back to the mapping screen and map your Begin and End Attach fields to our Begin and End Family fields.

  • Custodian name must be < 50 characters and restricted to letters, numbers, spaces, and [,._-"()]

    • Logikcull only accepts values in the the Custodian field that are 50 characters or fewer and use the accepted characters: [,._-"()]
      A value like this in the Custodian field would cause an error: Joe Cull;Jill Cull

    • The options to fix this are to either manually adjust the load file to remove the unsupported character, or to ask for a new load file from the producing party. The custodian field cannot be overlaid, so we recommend getting a new load file before proceeding with the upload.

  • Indicated parent BATES00000001 does not exist in the loadfile

    • There are several reasons this can happen. The most common is that the family fields are not mapped correctly.

    • Logikcull can pull the family information from mapping three fields: Begin Family, Begin Attach, and Family ID. Any of them can be used to populate the family relationship, however, not all of them have correct family information. For example, if Family ID is mapped but the values in that field do not have the correct parent information, this error will occur. To resolve, import any unnecessary or incorrect family fields as new (or do not import) to resolve these errors.

    • Sometimes, the family fields are simply incorrect. We do not recommend fixing these errors manually and would advise asking for a re-delivery of the load files with correct family information. Just like the custodian field, family information cannot overlaid, so we advise asking new load files before attempting the upload.

  • field "FileSize": Improperly formatted size, must be an integer representing the file size in bytes

    • This error occurs when a file size is not a whole number.

      • Supported file size format 12345

      • Unsupported file size format 123.45

    • The file size field can be imported as new and you can ask for an overlay with the field correctly formatted to a whole number.

  • Field x has length x, which exceeds the maximum size for an import field (30720)

    • This error means that whatever field you are attempting to import has values that exceed our maximum allowed field length. You will need to choose do not import on the field and go back to the producing party and ask for an overlay where the field is split up or truncated.

Did this answer your question?