(v1) .Imports v2.1.4.7

Imports

PCR-360 allows Users to Import information into the application as needed. The bottom of this page has a list of all the Import types that can be used. Individual pages handle the specific logic of any given Import. This page goes over the more general information related to Imports.

Creating a New Import

To create a new Import, see the Importing Data into the system wiki page.

Notes

• The Import process CANNOT DELETE records.
• In a Delimited file, the import treats the number of columns as one MORE than the number of commas separating values.
  • For example, if there is a CSV line with three commas, there will be 4 values.  The numbering of the fields is Zero-Based, so the indexes will be: 0,1,2,3 in the field mapping or Conditional Logic.
• In a Fixed Width file, you will define the fields by Position and Length.  The field positions are Zero-Based.  So in a file where a field starts on the 1st character of a line, the Position is entered as 0.  If the field starts on the 10th character, the Position is 9.
• To create a GLA Path, the value stored in the configuration option GLA_CONCATENATOR should be used as a concatenator.
  • The Default Value = " > ".
• To create any Hierarchy Path, the value stored in the configuration option GLA_IMPORT_CONCATENATOR should be used as a concatenator.
  • The Default Value = " > ".
• When running a Charge Import don't:
  • run a GLA Replace
  • Bulk Update Services/Equipment
• When running a Cabling Import don't:
  • run a Services/Equipment Bulk Update

Conditional Logic

• If you assign a Date type field in the Conditional Logic, the format is assumed to be in one of these formats: m/d/y or d-m-y.

User Defined Fields

Several tables in PCR-360 allow User Defined Fields (UDFs) to be added to them. The Import process that creates records for these tables does support the assignment of the UDF values. These cannot be mapped. They must always be assigned in the Conditional Logic section of the respective Import.

To assign a UDF value, you must know the Identifier name for the UDF. This is the value in the first column of the User Defined Fields grid.

For example, to assign the Rollover GLA Date from input field 4 in the GLA import, the assignment would look like this:

[GLA.UDF_ROLLOVERGLA68] = [4];

Where GLA is the table with the UDF and ROLLOVERGLA68 is the UDF Identifier.

The Identifier and table associations are verified by the Conditional Logic validations. If you use an invalid Identifier in the Conditional Logic, the Validate button or Save button shows the error when clicked, and you are not able to Save until valid data is entered.

Errors

Errors in Test Mode

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

1. 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.
2. User Defined Field (UDF) Import Save logic is done after the Save and is only done for non-test Imports. For this reason, UDF fields do not UPDATE or INSERT in test mode.

Errors that cause the import to Abort

If one of these errors occur, a Rollback will happen, which will undo any progress that was made before the problem.

• 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
• Database error
• SQL error
• Uploaded file is Empty

Related Pages