Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
outlinetrue
stylenone

Capability

The Equipment Import allows the User to INSERT new records and UPDATE existing Equipment records if a match is found.

...

If there is not an Equipment ID match, the Import attempts to match on the Serial Number. If there are multiple matches by the Serial Number, an error occurs.

MAC Address

If there is not a Serial Number match, the Import attempts to match on the MAC Address. If there are multiple matches by the MAC Address, an error occurs.


Note: Because of all of the different methods to lookup an existing record, some extra care must be taken when intending to update key fields of a record. For example, say you want to find a record by the Equipment ID, and update the Asset Tag. If the Asset Tag you provide already exists on a different record, then that different record will be found and updated instead. The lookup order is: Recid, Asset Tag, Equipment ID, Serial Number. Similarly, if you intend to create a new record and you provide an Asset Tag, Equipment ID, and Serial Number, if any of those values already exist, then that existing record will get updated instead of the new addition.

Fields

Asset Tag

Conditionally Requiredif the Equipment status is set to Installed AND the Asset Flag is set on the Equipment Catalog.

...

Equipment ID

Conditionally Requiredif the Equipment status is set to Installed.

...

If the Equipment's Status is Unassigned, it MUST be assigned to a Location that has the Warehouse flag set or has a blank (Null) Location value.

Part Number

Conditionally Requiredif the Import is doing an INSERT.

...

The Part Number field come from Equipment Catalog field not the full Catalog Path.

Units

Conditionally Requiredif the Has Units flag is set on the Equipment Catalog.

...

Parent Equipment ID

Datatype is Hierarchical String.

Should match an existing Equipment ID.

Look up is based on the Match On values for Equipment records.

Parent Location

Datatype is String

Optionally Used with Parent Equipment ID to identify a Parent Equipment.

Parent Location Type

Datatype is String

Optionally Used with Parent Location to identify a Parent Equipment.

Permitted values are from List Values of type LOCATION_TYPE: Site, Building, Floor, Room, Cube, Truck, Closet, Rack, Elevation, Manhole, or Warehouse.

Parent Asset Tag

Datatype is String

Optional method to identify a Parent Equipment.

Parent Serial Number

Datatype is String

Optional method to identify a Parent Equipment.

Parent MAC Address

Datatype is String

Optional method to identify a Parent Equipment.

Parent Equipment RECID

Datatype is Number

Optional method to identify a Parent Equipment.

Private

Data type is Boolean.

...

At least one Owner (either Customer Number, Dept Hierarchy Code, or Dept Hierarchy Name) may be be Required IF the following conditions are met:

...

Otherwise, the Owner field is is NOT Required Required.

Customer Number

Data type is String.

...

Dept Hierarchy Code

Data type is Hierarchical String or String.

Default value is blank.

...

Dept Hierarchy Name

Datatype is Hierarchical String or String.

Default value is blank.

The value for this field can be the full Hierarachial Path, or it can be just the last part of the Path. If you provide only the last part, then there is a chance that there could be duplicate values in the database. If duplicate values are found, then you will get an error.

Billing Group Override

Datatype is String

Value must match an existing Billing Group.

Eqp Condition

Default value is blank.

...

Parent Equipment

Datatype is Hierarchical String.

Default value is blank.

The value must be a unique Equipment ID if provided.

...

Default value is false.

Location

Conditionally Conditionally Required if the Import is doing an Insert AND the Location Required Flag is set on the the Equipment Catalog.

Datatype is Hierarchical String.

Location Type

Conditionally Requiredif the provided Location Name exists with multiple Types.

...

User entered values to the LOCATION_TYPE list may also be used.

New Location

Datatype is Hierarchical String.

Used to UPDATE the Location of an existing record, or INSERT a Location into a new record.

...

User entered values to the LOCATION_TYPE list may also be used.

Remarks

Datatype is String

Remarks are always appended to the Remarks list.

Author First Name

Datatype is String

Optional Author for the Remark. If provided, this value must match an existing Contact record.

This field will be ignored if there is no Remark value.

Author Last Name

Datatype is String

Optional Author for the Remark. If provided, this value must match an existing Contact record.

This field will be ignored if there is no Remark value.

Author Customer Number

Datatype is String

Optional Author for the Remark. If provided, this value must match an existing Contact record.

This field will be ignored if there is no Remark value.

GLA Expense Type

Datatype is String

The Expense Type of the GLA being provided. The value must be one of the List Values of type EXPENSE_TYPE: Default, Usage, Equipment, Labor, or any custom type.

GLA

Datatype is Hierarchical String.

Multiple GLA values can be provided on one input line. See the notes at the bottom of this page.

GLA Percent

Datatype is Number

Errors

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

  1. The value provided was found with multiple matches

    Toggle cloak


    Cloak
    • Error : Found multiple existing Equipment for Equipment ID '


  2. The value provided from another table is Inactive

    Toggle cloak


    Cloak
    • Error : Trying to use Inactive Charge Catalog <PART_NUMBER>


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

    Toggle cloak


    Cloak
    • Error : Missing Status for new Equipment'
    • Error : Missing or Invalid Units, and Charge Catalog specifies Units are required
    • Error : Missing or blank Location and Charge Catalog specifies Location is required
    • Error : Missing Part Number


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

    Toggle cloak


    Cloak
    • Error : Invalid Contact '<CUSTOMER_NUMBER>'
    • Error : Invalid Dept Hierarchy Name '<DEPT_HIERARCHY_NAME>'
    • Error : Invalid Dept Hierarchy Code '<DEPT_HIERARCHY_CODE>'
    • Error : Invalid Parent Equipment ID '<PARENT_EQUIPMENT>'
    • Error : Invalid Part Number '<PART_NUMBER>'
    • Error : Invalid Location '<LOCATION>'
    • Error : Invalid Location Type '<LOCATION_TYPE>'
    • Error : Equipment status is Unassigned but Location '<LOCATION>' is not a Warehouse


  5. The System was unable to save the record

    Toggle cloak


    Cloak
    • Error : Failed to save Equipment 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.


Notes

  • If attempting to UPDATE existing Equipment, none of these Required fields except the Match On fields are needed.
    For updates, it is assumed that the Required values are already entered. For updates, you only need to provide enough values to successfully find the Equipment record you are trying to update (Asset Tag or Equipment ID, and maybe Location).

  • If the Equipment Catalog has the 'Has Units' flag set, a Units value must be provided or an error happens.
    Units must be a positive integer or a zero. Null and negative values are not allowed. If the Equipment Catalog does not have the Has Units flag set to True [1], any provided Units value is ignored with no error or warning.

  • The Equipment import cannot associate Equipment to a Service. See the Service Import for a way to do this.

  • If you want to provide a single GLA, you can use the regular field mappings. If you want to provide multiple GLA values on one input line, you will need to use some Conditional Logic to create an array of values. This will let you provide GLAs for different Expense Types, and/or do split GLA Percentages.

Here is an example of how this is done:

Code Block
// Assign fields 13-18 into the GLA array
[FLAGS.GLA_ARRAY] = array(
   array(
      'Expense_Type' = [13];
      'GLA' = [14];
      'Percent' = [15];
      ),
   array(
      'Expense_Type' = [16];
      'GLA' = [17];
      'Percent' = [18];
   ),
);

Using this method, you can provide any number of sets of GLA values.

If you provide a set of GLA values, you must provide all 3 parts: the Expense Type, GLA, and Percent.

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.

Child pages (Children Display)
styleh6
sorttitle