1. Manual Recipient File Import

    1. The Recipient File can be imported manually at any time. This is a standard feature for WTS.

    2. Go to “Admin”.

    3. Select “Import Recipient CSV file” under “Data”.

    4. Choose if you want to clear previous Recipients and/or Locations (overwrite) from the database. If you choose to clear previous data, manually entered data in the system will be protected, all other data will be erased.

    5. Select “Backup Existing Data”.

    6. Locate recipient CSV file using “Choose File” (please refer to next section for help on how to prepare input CSV file).

    7. Select “Import File”.

    8. A progress bar will show under Import History under Advanced> Import Settings/History. It will also show how many entries were processed, updated and were added.

  2. Prepare Recipient CSV File

    1. In order to add new recipients to database or update existing ones, you can import data using a csv file. While adding/updating recipients, you can also add/update locations/routes in your database.
      You need to fill at least data for Recipient’s name (or First and Last Names) and Recipient’s location in a comma-separated Csv File. First line contains headers for each column.

      For example, 

      • 1st line : Name, Location 
      • 2nd Line : John Smith, Engineering

      If you choose not to erase existing data (recipients and locations) from database, then CSV file will only contain new recipients and existing recipients that you wish to modify. If a recipient or a location already exists in the database, it will be updated after import.
      For example, if “John Smith” has already been added to recipients’ list, when following csv file is imported, then his information will be updated in database.

      • 1st line : Name, Location, City, Phone, Email, Company, Department, ZIP, Cell 
      • 2nd line : John Smith, Engineering, Paris, 049494949, zzz@gmail.com, NEOPOST, Electrical, 92220, 0393399393

      If location field contains a new value, then it will be added automatically to the list of available locations and can be consulted in “Admin > Manage Routes” page.
      If you select “Clear Previous Recipients from Database first?” or “Clear previous location from Database first”, then all data will be erased from database before import adds new recipients and new locations.

  3. Import Recipient CSV file and construct routes at the same time

    1. In addition to importing single locations, the WTS importer is capable of importing a Location tree if Routing is active on the account. Location tree header titles may be included in standard imports and allow for quick addition of complex routing structures. A few rules govern the structure of location tree import.

  4. Rules for the Routing Tree Import

    1. There are 4 types or tiers of definition in a WTS location tree, with the 4th (fourth) and most definitive, being a combination of the Room and Location.

      • The tiers are labeled as follows:
        Tier 1: City ; Tier 2: Building* ; Tier 3: Floor ; Tier 4: Room # Location**
        Requires BuildingCode header title in import to display properly in WTS
        Requires LocID header title in import to display properly in WTS.
      • ID's must be unique.
    2. HEADERS:

      Lastname,Firstname,ID,BadgeID,City,Building,BuildingCode,Floor,Room,Location,LocationCode,Mailboxno,Email,Cell,Classification

      DATA:

      Smith,John,001,001,City 1,Building 1,C1B1,Floor 1,Room 1,Location 1,C1B1F1R1L1,MB001,jsmith@company.com,,Employee
      Smith,Jane,002,002,City 1,Building 1,C1B1,Floor 1,Room 1,Location 2,C1B1F1R1L2,MB002,,222-222-2222,Employee
      Doe,Jane,003,003,City 1,Building 1,C1B1,Floor 1,Room 2,Location 3,C1B1F1R2L3,MB003,,333-333-3333,Employee
      Doe,John,004,004,City 1,Building 1,C1B1,Floor 1,Room 2,Location 4,C1B1F1R2L4,MB004,jdoe@company.com,444-444-4444,Employee

      Converted Example in Excel:

  5. Field Descriptions for Location Tree

    1. City- Level 1 - needs to be part of City, Building Code, and LocCode
      Building- Level 2 - needs to be part of Building, Building Code, and LocCode
      *Building Code - (not a level) - consists of City and Building used in the database for identification

      Floor- Level 3 - needs to be part of Floor and LocCode
      Location- Level 4 - needs to be part of Location and LocCode

      Room- Level 5- show on level 4 and adds to the Location- a part of Room and LocCode

      *LocCode- (not a level)-consists of City, Building, Floor, Location and Room- used in the database for identification
      *Required when using Routing

      Location Tree produced from above data

      City 1
      Building 1
      Floor 1
      Room 1 # Location 1
      Room 1 # Location 2
      Room 2 # Location 3
      Room 2 # Location 4
      Floor 2
      Room 1 # Location 5
      Room 1 # Location 6
      City 2
      Building 1
      Floor 1
      Room 1 # Location 1
      City 3
      Building 1
      Floor 1
      Room 1 # Location 1
      City 4
      Building 1
      Floor 1
      Room 1 # Location 1

    2. Buildings and Locations with the same name are permitted to exist because they have different ID's. These are not the same types repeated.

      Types do not need to follow the City, Building, Floor, Room, naming schema as long as their header titles follow the requirements from the "List of Import Header Titles".

Date created:
07/31/2018 09:38:41
Last updated:
02/21/2019 10:27:40
Product(range):
WTS Package Tracking
Print