Errors

Import Errors Grid example

The Error Description on the Import Files Grid is only populated when the Import Process encounters an Error that requires the entire file to cease being processed. Errors on the Import Files Grid should be a rare occurrence, usually being empty files or when a file does not match up with the expected format.

The Imported Records/Import Errors Grids will display any Errors on individual line items that triggered an error in the process but did not require the entire process to stop. It is recommended that after Importing a File, one of these two Grids should be checked to confirm nothing unexpected went wrong within the File.

Note: If you ever see an error on the Import Files grid that you do not understand, it should be reported to PCR immediately so that we can dig into the issue further, as that might be indicative of a bug within the Import Process.

A quick check that could be done on the Import Files Grid, to see if the Import File might have had an error, would be to check the "Record Count" and "Added Count". The "Record Count" indicated how many lines the File has that will be processed, while the "Added Count" indicates how many records were successfully saved to the system.

Note: Imports like Calls and Usage, are expected to add so many records to the system that these types of Imports do not add details to the Imported Records Grid. These Imports have their own Details and Errors Grids under View/Report for Billing.

Errors in Test Mode

When you run the Import in Test mode, there are two kinds of errors that do not report.

If the Save to the database failed for an unexpected reason, the errors do not generate. The Import can’t detect these errors until the save is attempted, which does not happen in Test mode.
User Defined Field (UDF) Import Save logic is done after the Save and is only done for non-test Imports. For this reason, any errors processing the UDF values will not be reported in Test Mode.

Errors that cause the import to Abort

If one of the following errors happens, the import process will abort. Because each successful import line is always committed, if the import process aborts halfway through a file, the result is the first half of the file will still be processed and committed.

Database error
SQL error
Uploaded file is Empty

Handling Errors

When an Error status shows on the Imports grid the reprocess option should be used. For some imports (Calls, Usage, GLA Charges and Service Charges), this cleans-up any commits made during the previous attempts that would be problematic and reattempts the Import. It is not recommended to re-upload files, due to the risk of the creation of duplicate records. This is particularly important on all Charges Imports. If you need to make a change to the file and re-upload instead of reprocessing, make sure to remove previously imported lines.

The following Imports Formats do not update existing records and potentially could create duplicates:

The following Imports Formats are typically used to create new records but can be used to update as well:

Other Common Errors

There are certain common errors that do not cause the import to abort. These errors are common to all Import Formats.

Value not present in lists table
Error reading column using format mask
Column defined as a number contains non-numeric data
Column position not present in line
Column index not present in line

There are other errors that are specific to the import types, these are listed on the individual import pages.

Browser not supported