Problem

1. The system was unable to read the file you selected for import.
   

How to Fix

1. Check File Location: Make sure the file still exists in the specified location.
2. Check Permissions: Verify you have the necessary permissions to read the file.
   

Problem

1. The first row (header row) of your file contains duplicate column names. Every column must have a unique header.
   

How to Fix

1. Edit the Source: Open your import file.
2. Rename Columns: Find the duplicate column name mentioned in the error message and rename one of them to make it unique (e.g., rename "Notes" to "Notes_Extra").
   

Problem

1. The import is configured to sort rows, but the specific settings for the sort (like the column name or direction) are missing or invalid.
   

How to Fix

1. Check Configuration: Go to the import configuration settings.
2. Verify Sort Settings: In the "Data Processing" section, find the sort options. Ensure you have correctly specified a Column to sort by and a Direction (Ascending or Descending).

Logged Message Example

Problem

1. The system could not find the column specified in the sort settings within your data file's headers.
   

How to Fix

1. Check Configuration: Note the exact "Column" name in your import's sort settings.
2. Inspect Headers: Check the actual column headers in your source file.
3. Correct the Mismatch: Either change the column name in the configuration to match a header in your data, or change the header in your file to match the configuration. The names must match exactly.
   

Logged Message Example

Problem

1. An error occurred during the actual data sorting process, usually caused by inconsistent or problematic data within the sort column, such as mixing text and numbers, or unexpected blank values.
   

How to Fix

1. Inspect the Data: Open your source file and carefully examine all values within the column being used for the sort.
2. Clean the Data: Correct any mixed data types (e.g., remove "N/A" from a number column) or special characters.
   

Problem

1. There is an issue with the "Match On" setting in your Person Matching Rules. This could mean the setting wasn't selected correctly or an issue occurred while preparing the ID data for matching.
   

How to Fix

1. Verify "Match On" Setting: In your import configuration, ensure you have selected the correct field (e.g., Proprietary ID, Local ID) that corresponds to the IDs in your file.
2. Check Data Quality: Ensure the IDs in the matching column of your file are clean and consistently formatted.
   

Problem

1. The import was automatically stopped as a safety measure because either zero records or a critically low percentage of records in your file could be matched to people in the system.
   

How to Fix

1. Verify Configuration: This is the most common cause. Double-check that the 
2. ID Column Name and the Match On setting are both correct.
3. Check File Data: Open your file and compare the format of the IDs to the IDs on existing people in the system.
4. Review Match Options: Ensure settings like "Ignore Leading Zeros" are set correctly for your ID type.
   

Problem

1. After successfully matching rows to people, the system found no actual data to import. This happens if all the mapped fields in your file were blank and "Import Blank Values" was turned off, or if all potential updates failed due to data errors.
   

How to Fix

1. Review File Data: Check that the columns you intend to update actually contain values.
2. Check "Import Blank Values" Setting: If you intend to clear fields with blank values, ensure this option is enabled.
3. Look for Warnings: Check the import logs for warnings that might indicate specific data processing errors, like invalid date formats.
   

Problem

1. An unexpected error occurred while the system was trying to save the imported data to the database. This is often a temporary system issue rather than a problem with your file.
   

How to Fix

1. Retry the Import: Wait a few minutes and try running the import again.
2. Contact Support: If the error happens repeatedly, contact the support team with the error code (E0010), file name, and the time the error occurred.
   

Problem

1. The system failed to find or load the field mapping rules for the specified Alias. This could be because no fields have been mapped for that Alias, or there's an issue with the configuration itself.
   

How to Fix

1. Verify Import Alias: Double-check that the Alias you are using is correct.
2. Check Form Mapping: An administrator should confirm that fields are actually mapped to this Alias in the Form Editor and that the mapping expressions are valid.
   

Problem

1. The system could not determine the file's format or structure. This may be due to a corrupted file, incorrect delimiter, or missing header row.
   

How to Fix

1. Inspect File Manually: Open the file in a text editor to see if the content looks correct and matches the expected format.
2. Validate Structure: Compare the file's structure (columns, headers, delimiters) against the requirements for this import.
   

Logged Message Example

Problem

1. A critical system setting that defines the base file path is missing.
   

How to Fix

1. An administrator must ensure the FTPRoot path is correctly defined in the application's configuration settings.
   

Logged Message Example

Problem

1. The system could not find the file at the specified location.
   

How to Fix

1. Verify File Existence: Ensure the file exists in the directory indicated in the error message.
2. Check Path: Confirm that the path, including the folder and filename in your Import Configuration, is correct.
   

Logged Message Example

Problem

1. The system found the file but couldn't read its contents, possibly due to file corruption or the file being locked by another program.
   

How to Fix

1. Check File Integrity: Try opening the file yourself to see if it's corrupted.
2. Check for File Lock: Ensure the file is not open and locked by another application.
   

Logged Message Example

Problem

1. The system opened the file but found it contained no data.
   

How to Fix

1. Check File Content: Open the file and verify that it contains data.
2. Check Generation Process: If the file is generated automatically, check the process that creates it.
   

Logged Message Example

Problem

1. The import is configured to use a transformation, but the XSLT template is missing or has no published content.
   

How to Fix

1. Publish XSLT: Ensure a valid, non-empty XSLT template has been published in the Transformation Editor.
2. Disable if Unneeded: If transformation is not required, disable the "Enable Data Transformation" option in the import configuration.
   

Logged Message Example

Problem

1. A fundamental element required for the file-to-XML conversion was missing, such as the file content itself or a valid header row for a CSV/TSV file.
   

How to Fix

1. Check File Content: Ensure your file is not empty.
2. Check CSV/TSV Headers: Ensure the file contains a valid header row with non-empty column names as the first line.
   

Logged Message Example

Problem

1. The content of your file does not adhere to the expected syntax for its format (JSON, XML, CSV). The logged message usually gives specific details, often including line and position numbers.
   

How to Fix

1. Validate Your File: Use an online validator (e.g., a JSON or XML validator) to check for syntax errors like missing commas, brackets, or unclosed tags.
   

Logged Message Example

Problem

How to Fix

Logged Message Example

Problem

1. An unforeseen error occurred while preparing the file content for transformation. This is a catch-all for issues not covered by more specific errors.
   

How to Fix

1. Retry: This might be a temporary system glitch, so a retry may work.
2. Contact Support: If it persists, contact support with the full error message.
   

Logged Message Example

Problem

1. The XSLT stylesheet contains a syntax error or is incompatible with the source XML. The message usually comes directly from the XSLT processor and can be technical.
   

How to Fix

1. Debug the XSLT: The stylesheet needs to be reviewed for issues like incorrect XPath expressions or namespace problems.
2. Test Locally: Use an external XSLT development tool to test the stylesheet against the source XML to isolate the problem.
   

Logged Message Example

Problem

1. The XSLT transformation completed, but the resulting output was not a well-formed XML document.
   

How to Fix

1. Review the XSLT: Check the stylesheet to ensure it's designed to produce well-formed XML. Check for invalid characters or unclosed tags.
2. Validate the Output: Test the transformation in a development tool and validate its output with an XML validator.
   

Problem

1. An unforeseen error occurred during the XSLT transformation process that wasn't a specific XSLT or XML parsing error, possibly due to large data volumes or memory issues.

How to Fix

1. An administrator or XSLT developer should investigate, possibly by trying the transformation in a controlled environment.
   

Logged Message Example

Problem

1. The initial file had content, but the processing rules (most commonly an XSLT transformation) filtered out or failed to match any data, leading to an empty output.

How to Fix

1. Check the Transformation Logic: This is the most likely cause. Your XSLT template may not be correctly matching the nodes in your source XML. Check your XPath selectors (<xsl:for-each select="...">, etc.) for typos or incorrect paths.

Logged Message Example

Problem

1. The system could not process your CSV file because it contains a structural or formatting error, such as duplicate headers or a malformed line with an incorrect number of quotes or commas.
   

How to Fix

1. Inspect Column Headers: Carefully check the first row for any duplicate column names.
2. Examine for Formatting Errors: Look for stray quotation marks or lines that have a different number of commas than the header row. The logged error message may give a line number to help locate the problem.
   

Logged Message Example

Problem

1. The text provided for the "Sort By" setting in the configuration is not in the required JSON format.
   

How to Fix

1. Correct the Format: The value must be a valid JSON object with "Column" and "Direction" properties, like {"Column": "LastName", "Direction":"ASC"}. Pay close attention to double quotes and commas.