SIS Import Error "Could not parse file:"


To view Import Errors in SIS Integration Administration, click here.

Import Error "Could not parse file: " means that there is an issue in the source data/csv file that is causing the data extract (Json file) to be invalid or missing from the SIS Import Job process, preventing "fresh" data from importing into SS&E.

  • New data will not import from the SIS into SS&E on this data feed until this issue is resolved.

Upon finding this error message, the SIS Import Job is most likely running and completing successfully, and most likely the associated data stream is NOT displaying as out of date.

However, this error message most likely means that the most recent data extract is invalid and the system is unable to import "fresh" data from this data feed data extract file into SS&E.


In most cases, downloading the most recent data extract on file from SIS Integration -> Datafeeds will help show what exactly is causing this import error message.

For example:

  • Opening the data extract may show formatting errors, invalid characters that need to be resolved.
  • Opening the data extract in Notepad++ and scrolling through required fields may show that data is importing as null on a required field. To view which fields are required on each data feed, click here.

The message displayed on the SIS Integration- Import Errors page will most likely explain why the data extract (Json file) is invalid.

This error message usually indicates data-related issues, for example a bad character or invalid format preventing the data extract from being processed.

To fix this error message, the SIS source data/Informer reports/csv files/data extract definitions must be reviewed so that the issue is fixed where it first occurs.

Once resolved so that the data extract/Json file is no longer invalid, this will allow fresh data to be imported into SS&E.

  • To make sure the issue is resolved and SIS data is importing successfully, wait for the next SIS Import cycle and verify that the Import Error(s) stop displaying on the Import Errors menu.
  • This should be verified after the data extract is fixed and after the next Connect Job and SIS Import Job complete.

Note: It is important to fix the source data where the root cause of the issue initiates so that the import file is permanently fixed. Fixing the problem(s) in the data extract (Json file) on file (that can be downloaded from SIS Integration Datafeeds Administration) will not fix the root cause and a new "invalid" data extract will be generated every time the SIS Import Job is scheduled to run.

Once the issue is identified and resolved at the source, fresh data will flow from the SIS into SS&E.

Was this article helpful?
0 out of 0 found this helpful

Articles in this section

See more
How to Contact Support
There are many ways to reach out! Click here for our support options.
Watermark Academy
Click to access the Watermark Academy for consultation, training, and implementation companion courses.