FAQ KB0394601
Email
Import Legacy Contracts: What is causing "NoSuchElementException: null" error?
Question

What is causing the import legacy contracts error, NoSuchElementException: null

Answer

In most instances, there is an issue in field data that contains large amounts of text. When this error is encountered, near the end of a field value of long text there are multiple quotation marks ("), and these cause the delimiters of the columns to become unstable. In the affected row of data, a new column that is missing a header is created because of the quotation marks interrupting the delimiters.

An example that caused an issue is:

We the People of the United States, in Order to form a more perfect Union, establish Justice, insure domestic Tranquility, provide for the common defense, promote the general Welfare, and secure the Blessings of Liberty to ourselves and our Posterity, do ordain and establish this Constitution for the "United States of America."

The quotation marks around United States of America can interrupt the way the comma-separated value (CSV) loads because they interrupt the comma field separators, causing an attempts to make a new column within that row that has no header value.

To correct the issue, remove the quotation marks near the end of the string and re-import.

Additional Information

To know where to find the bad data in the Contracts.csv file, view the import error log in Manage > Administration > Project Manager > Import Legacy Contracts Status. Scroll to the bottom of the import log to find the error message. Then, check in the row of data that appears after the last successful update/creation row per the log.


Applies To

Strategic Contracts

Terms of Use  |  Copyright  |  Security Disclosure  |  Privacy