Page Comparison

Capability

This Import allows the User to Import GLA Components into the GLA Components grid and use them in the GLA Catalog. The Import will INSERT or UPDATE as appropriate.

Matches ON

The GLA Component Import matches on the Code and Component fields of the Import File.

Fields

Code

Required

Datatype is String

Component Type

Required

Datatype is String

Description

Datatype is String

Status

Datatype is Boolean

Defaults to "Inactive" [0]

All other values enter as "False". [0]

Format

Datatype is String

The Format is NOT saved.

It is just used to inform the Import process which GLA Format this Code is for.

If this is not provided, the default GLA Format is used as set from the Configuration file.

Child Records

There are no Child records associated with GLA Components Import.

Flags / Conditional Logic

There are no Flags or Conditional Logic associated with the GLA Components Import.

Errors

When an Import Line fails, it is usually because the Line falls into one of the following categories:

1. A blank value was provided, for a field with a required value

   Toggle cloak

   Cloak
   "Error: Component Type is missing or blank" "Error: Component Code is missing or blank"

   
   

2. The value provided is not acceptable for the record type being created

   Toggle cloak

   Cloak
   "Error: GLA Format '<format>' is not valid" "Error: Invalid Component Type '<COMPONENT_TYPE>'"

   
   

3. The System was unable to save the record

   Toggle cloak

   Cloak
   "Error: Failed to save GLA Component record; <errorMessage>" If you experience any of these Errors, without another accompanying Message about what might have caused the Save Failure, please submit a Ticket to PCR.

   
   

UDF Associations

User Defined Fields on any given Import are all handled the same way with Conditional Logic. For more information about adding a UDF to the Import, see the User Defined Fields section of the Imports main page.