Unable to upload documents and options


This article provides guidance if you receive the error “Unable to upload documents and options.” when importing data.

 

If this occurs, please try the following:

  1. Try re-uploading the import mapping file. (Especially if you have just uploaded the mapping file and this is your first attempt to use it.)
  2. Try importing the data into a new/different project. (Especially if the import mapping had been working, but suddenly stopped working.)
  3. If you get this error when importing a gINT Project File, open the file in gINT and run Utilities>Repair/Compact Databases on the file. Then retry importing the file. (Especially if the mapping file is working for other Project Files, but failing for a specific file.
  4. Try removing any parentheses from the file name.
  5. If none of those options work, please contact the support team to troubleshoot further.

The above suggestions are not guaranteed to resolve the error - the error message can occur from an issue within the mapping file and/or data file. However, the error is often a result of issues in the mapping file upload process, or some project-specific issue. So, it’s recommended to try the suggestions above before troubleshooting the mapping file further.

If the above suggestions did not resolve the issue, some other things to check to troubleshoot further include:

  1. Review your mapping file and ensure you do not have a mapping where the field mode is 'Evaluate' and there is a 'source' mapping. 'Evaluate' mappings should have an 'expression' instead. Similarly, check to make sure you don't have any mappings where the field mode is 'Copy' and there is an 'expression' mapping. 'Copy' mappings should have a 'source' instead.
  2. Check the mapping file for fields accidentally marked as key="true" that are not key fields.
  3. Check the mapping file to ensure any expressions using the various "Lookup...()" functions are using the proper syntax. The Example Files are a good place to look to check for the proper syntax.
  4. Make sure a mapping is supplied for the LocationDetails.LocationType field.