...
Open the 'Admin' tab and click on the node labeled 'File Management'. Then, click on the node labeled 'Import Files'. Next, click on the node labeled 'Upload Import Files'.
In the form, the User must select an 'Import File Format' from a list of items on the Import File Formats grid.
...
To deleted Files that have been imported, go to Admin > Imports / Exports / Import Files > Import Files.
Once there, select the desired files to be deleted, and click 'Delete Selected' from the Import Files Grid.
A confirmation dialogue will appear, alerting the user what types of files can be deleted.
...
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
Errors
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.
| Include Page | ||||
|---|---|---|---|---|
|