Versions Compared

Old Version 12

changes.mady.by.user Karis Hathaway

Saved on

compared with

New Version Current

changes.mady.by.user David Engblom

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from this space and version 2023.1

...

Datatype is String

Status

Datatype is Boolean

Defaults to "Inactive" [0]

Permitted Values: "1", "True", "Active", or "Yes" sets the Flag to True [1].

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

...

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

Errors

The following errors display if the record Save fails:

"Error: GLA Format '<format>' is not validWhen 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>'"
...

  2. 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.
...