...
This field CANNOT UPDATE.
The full Location hierarchy in a single string with individual parts of the Location Hierarchy separated by
...
the HIERARCHYPATH_CONCATENATOR.
Multiple levels of a hierarchy "path" (like Locations, GLAs, and Catalogs) are connected by the HIERARCHYPATH_SEPARATOR string.
The default value for this string is right angle-brace (>) with a space on either side: " > ".
When importing nested Locations, the separator you use for each level of the hierarchy must match the concatenator string.
For example, Site A > Building B > Room C.
...
Permitted values are from the LOCATION_TYPE List Values.
This field is used for the Parent Location lookup if provided.
...
Permitted values must be one of List Values of type LOCATION_TYPE: Site, Building, Floor, Room, Cube, Truck, Closet, Rack, Elevation, or Manhole.
User entered values to the LOCATION_TYPE list may also be used.
If a Location Type is provided, the Import uses that Location Type to see if an existing record exists for UPDATE.
...
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.