...
Full Location
Required
Datatype is Hierarchical String.
This field CANNOT UPDATE.
The full Location hierarchy in a single string with individual parts of the Location Hierarchy separated by the HIERARCHYPATH_CONCATENATOR.
If an existing Full Location field is not found or the Location string exists with multiple Types, the Import generates an error.
...
Permitted values are from the LOCATION_TYPE List Values.
This field is used for the Parent Location lookup if provided.
...
Default Warehouse
Datatype is Hierarchical String.
Sets the Default Warehouse for the Location to use.
...
Default Return Warehouse
Datatype is Hierarchical String.
Default value is blank.
Sets the Default Warehouse for the Location to use.
...
Equipment Location
Datatype is Hierarchical String.
Equipment Location is used by the Import to look up existing Equipment.
...
Equipment Service Catalog
Datatype is Hierarchical String.
This is only used if an Equipment ID is also provided.
...
- True: Any existing Equipment is unchanged, and new Equipment is appended to the Servicing Equipment associations.
- False: Any existing Equipment is removed from the Servicing Equipment list, and the new Equipment is added.
Note: This means the Import only leaves the LAST Equipment record from the Import File associated on as the Servicing Equipment on that Location.
Errors
The following is a listing of the Errors and Warning that are generated by the Locations Import.
The following errors are displayed if the Location INSERT or UPDATE fails:
When an Import Line fails, it is usually because the Line falls into one of the following categories:
A blank value was provided, for a field with a required value
Toggle cloak Cloak - Error : Missing Location
- Error : Missing or Blank Location Type for new Location <FULL
...
- _
...
- LOCATION>
- Error : Missing Service Catalog <SERVICE_CATALOG> for Equipment ID <EQUIPMENT_ID>
...
The value provided is not acceptable for the record type being created
Toggle cloak Cloak - Error : Invalid Parent Location Type '<LOCATION_TYPE>'
- Error : Invalid Default Warehouse Type '<LOCATION_TYPE>'
- Error : Invalid Default Return Warehouse Type '<LOCATION_TYPE>'
- Error : Equipment Location Type '<LOCATION_TYPE>'
These do NOT cause the Location INSERT or UPDATE to fail. They are non-essential for the Location or they happen after the Location save.
...
The value provided was not found in the database
Toggle cloak Cloak - Warning : Invalid Default Warehouse '<DEFAULT_WAREHOUSE>'
- Error : Invalid Parent Location '<parentLocation>'
- Error : Invalid Equipment Location <EQUIPMENT_LOCATION> for Equipment ID <EQUIPMENT_ID>
- Error : Invalid Equipment for Equipment ID <EQUIPMENT_ID> in Location <EQUIPMENT_LOCATION>
The System was unable to save the record
Toggle cloak Cloak - Error : Failed to save LocationsSvcEquipment record; <errorMessage>
- Error : Failed to save Address record; <errorMessage>
- Error : Failed to save Location 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.
...