Importing Data - Revision history

40.141.82.4 at 14:01, 23 January 2015

2015-01-23T14:01:42Z

40.141.82.4 at 14:00, 23 January 2015

2015-01-23T14:00:59Z

Dgallagher: /* Importing Data */

2014-09-02T22:55:24Z

‎Importing Data

Dgallagher: /* Importing Data */

2014-09-02T22:48:07Z

‎Importing Data

Dgallagher: /* Importing Data */

2014-09-02T20:38:26Z

‎Importing Data

Cheryl Deuser: /* Importing Data */

2012-09-05T19:19:13Z

‎Importing Data

Dale Swanson: /* Importing Data */

2012-08-18T15:48:24Z

‎Importing Data

Dale Swanson: /* Importing Data */

2012-08-18T15:47:25Z

‎Importing Data

Dale Swanson: Created page with "== Importing Data == Data can be imported into SQBX as either part of your account's initial set-up or as part of a recurring administrative task to keep data synchronized wi..."

2012-08-18T15:46:43Z

Created page with "== Importing Data == Data can be imported into SQBX as either part of your account's initial set-up or as part of a recurring administrative task to keep data synchronized wi..."

New page

== Importing Data ==

Data can be imported into SQBX as either part of your account's initial set-up or as part of a recurring administrative task to keep data synchronized with a back-end system.

All Imports are handled via CSV (Comma Separated Values) file.

Importing Recipients

The CSV File needs a header listing the column names.
There should be the same number of columns throughout the file as mentioned in the header.

The Data is mapped as follows.

(Where there are multiple Accepted fields, they will be concatenated and comma delimited in the order shown here,

<table width="80%" border="1" cellspacing="0" cellpadding="4px">

<tr>
<th width="30%">SQBX Field</th><th colspan = "4">Accepted Fields</th><th width="10%">Mandatory</th>
</tr>

<tr>
<td rowspan="4">Import Code

(A code used to uniquely identify a recipient between systems. Must be unique) </td><td colspan="4">Id</td><td rowspan="4">No- although advisable</td>
</tr>
<tr>
<td colspan="4">Code</td>
</tr>
<tr>
<td colspan="4">RecipientNo</td>
</tr>
<tr>
<td colspan="4">EmployeeNo</td>
</tr>
<tr>
<td rowspan="3">Assigned Code (A code assigned to a badge or other identifying item)</td><td colspan="4">BadgeId</td><td rowspan="3">No- Used on Handheld for Rapid Package Retrieval</td>
</tr>
<tr>
<td colspan="4">CurrentCode</td>
</tr>
<tr>
<td colspan="4">SecurityCode</td>
</tr>
<tr>
<td rowspan="3">Location Code

(A code to uniquely identify locations between systems. Used to find recipient locations during the import.)</td><td colspan="4">LocId</td><td rowspan="3">No- although advisable</td>
</tr>
<tr>
<td colspan="4">LocCode</td>
</tr>
<tr>
<td colspan="4">LocationNo</td>
</tr>

<tr>
<td rowspan="2">Building Code

(A code to uniquely identify buildings between systems. Used as an alternative to the LocationNo field. Use in conjunction with Recipient Room and Recipient City to automatically generate the Location Tree during the import.)</td><td colspan="4">BuildingCode</td><td rowspan="2">No- although advisable for tree import.</td>
</tr>
<tr>
<td colspan="4">OfficeCode</td>
</tr>

<tr>
<td rowspan="2">Recipient Name</td><td colspan="4">Name</td><td rowspan="2">Yes</td>
</tr>
<tr>
<td colspan="2">Lastname</td><td colspan="2">Firstname</td>
</tr>
<tr>
<td rowspan="2">Recipient Location</td><td colspan="4">Location</td><td rowspan="2">Yes</td>
</tr>
<tr>
<td colspan="4">Site</td>
</tr>
<tr><td rowspan="3">Location Description</td><td colspan="4">Locdesc</td><td rowspan="3">No</td></tr>
<tr><td colspan="4">Description</td></tr>
<tr><td colspan="4">Desc</td></tr>
<tr>
<td rowspan="3">Recipient Phone</td><td colspan="4">Phone</td><td rowspan="3">No</td>
</tr>
<tr>
<td colspan="4">Extention</td>
</tr>
<tr>
<td colspan="4">Ext</td>
</tr>
<tr>
<td rowspan="3">Recipient Cell Phone</td><td colspan="4">Cell</td><td rowspan="3">No</td>
</tr>
<tr>
<td colspan="4">Cellphone</td>
</tr>
<tr>
<td colspan="4">Mobile</td>
</tr>
<tr>
<td >Send SMS - Allows fine tuning of SMS system per recipient. (Only used if Cell phone is provided. If Send SMS field is not included in the file, SQBX Defaults to 1.)</td><td colspan="4">SendSMS</td><td>No</td>
</tr>
<tr>
<td >Recipient Fax</td><td colspan="4">Fax</td><td>No</td>
</tr>
<tr>
<td rowspan="2">Recipient Room</td><td colspan="4">Room</td><td rowspan="2">No</td>
</tr>
<tr>
<td colspan="4">Office</td>
</tr>
<tr>
<td rowspan="1">Recipient Address</td><td colspan="4">Address</td><td rowspan="1">No</td>
</tr>
<tr>
<td rowspan="1">Recipient Address - Line 2</td><td colspan="4">Address2</td><td rowspan="1">No</td>
</tr>
<tr>
<td rowspan="1">Recipient City</td><td colspan="4">City</td><td rowspan="1">No</td>
</tr>
<tr>
<td rowspan="2">Recipient State</td><td colspan="4">State</td><td rowspan="2">No</td>
</tr>
<tr>
<td colspan="4">County</td>
</tr>
<tr>
<td rowspan="2">Recipient Zip/Postcode</td><td colspan="4">Zip</td><td rowspan="2">No</td>
</tr>
<tr>
<td colspan="4">Postcode</td>
</tr>
<tr>
<td >Recipient Email</td><td colspan="4">Email</td><td>No</td>
</tr>
<tr>
<td >Send Email- Allows fine tuning of Email system per recipient. (Only used if Email Address is provided. If Send Email field is not included in the file, SQBX Defaults to 1.)</td><td colspan="4">SendEmail</td><td>No</td>
</tr>
<tr>
<td >Recipient Company</td><td colspan="4">Company</td><td>No</td>
</tr>
<tr>
<td rowspan="2">Mailbox Number</td><td colspan="4">Mailbox</td><td rowspan="2">No</td>
</tr>
<tr>
<td colspan="4">Mailboxno</td>
</tr>
<tr>
<td rowspan="2">Classification</td><td colspan="4">Classification</td><td rowspan="2">No</td>
</tr>
<tr>
<td colspan="4">Type</td>
</tr>
<tr>
<td rowspan="2">Department</td><td colspan="4">Dept</td><td rowspan="2">No</td>
</tr>
<tr>
<td colspan="4">Department</td>
</tr>
<tr>
<td rowspan="2">Costcenter</td><td colspan="4">Costcenter</td><td rowspan="2">No</td>
</tr>

</table>

'''Existing recipients will be updated where possible.'''

If the '''import code''' is supplied, the recipient can be accurately matched.
The import code can be anything, as long as it's unique.
It can be an employee number or any other type of unique identifying code. This is important for ensuring that changes to names are respected.

If the Import Code is not supplied, the existing recipient is matched based on their '''name and location''' (to prevent 2 John Smiths at 2 locations being confused as the same person).
This is not as accurate as using an Import Code and may lead to duplicates where someone has moved location or changed their name.

The '''Location Code''' is used to find locations previously imported or added into the SQBX system.

In most cases, the location list will have been massaged into a very useful tree structure and the recipients lovingly placed in their correct locations.
By using the import codes for both recipient and location, the existing tree structure is preserved and recipients are moved to their new locations.

Any Locations not found within the Delivery locations list will be added during the import. However, they will not be placed in any particular branch of the location tree, this will have to be done manually after the import. However, if the location was added using an import code, their position in the tree will be retained during future imports.

There is a way to import the location tree during the recipient import.
By supplying a Building Code, a Room No and a City, the Importer will create the relevant tree structure when creating the locations.

This example import will achieve this.
<div style="border:1px solid #aaaaaa;background-color:#eeeeee;padding:4px;">
'''Code,BuildingCode,Site,LastName,FirstName,Extension,Room,,Company,City,State'''

E0001,CDH,Discovery House,Samson,Dale,0122,31,ACME UK,Cambridge,Cambridgeshire

E0008,CDH,Discovery House,Gibson,Larry,0113,30,ACME UK,Cambridge,Cambridgeshire

E0120,NFH,Fulcrum House,Ekhart,Dean,0148,300,ACME UK,Nottingham,Nottinghamshire

E0023,WSF,Swallow House,Harris,Jason,0123,7,ACME UK ,Wyboston,Bedfordshire

E0025,WSF,Swallow House,Jones,Martin,0123,8,ACME UK,Wyboston,Bedfordshire

E0029,SFH,Safford Hall,Beird,Andrew,120,105,ACME UK,Stone,Staffordshire
</div>

This will create the following tree

*Cambridge
**Discovery House
***Discovery House #30
***Discovery House #31
*Nottingham
**Fulcrum House
***Fulcrum House #300
*Wyboston
**Swallow House
***Swallow House #7
***Swallow House #8

[[Main_Page|Back to Main Page]]

@@ Line 23: / Line 23: @@
          <td rowspan="4">Import Code
-             (Identifier. A code used to uniquely identify a recipient between systems. Must be unique. Helps alleviate recipient duplicates.) </td><td colspan="4">Id</td><td rowspan="4">Recommended- If utilizing Importing Recipients more than once </td>
+             (Identifier. A code used to uniquely identify a recipient between systems. Must be unique. Helps alleviate recipient duplicates.) </td><td colspan="4">Id</td><td rowspan="4">Highly Recommended- If utilizing Importing Recipients more than once </td>
      </tr>
      <tr>

@@ Line 163: / Line 163: @@
      </tr>
      <tr>
-         <td  rowspan="2">Costcenter</td><td colspan="4">Costcenter</td><td rowspan="2">No</td>
+         <td  rowspan="1">Costcenter</td><td colspan="4">Costcenter</td><td rowspan="1">No</td>
      </tr>
      <tr>
-         <td  rowspan="2">Forwarding Label</td><td colspan="4">Forwardinglabel</td><td rowspan="2">No</td>
+         <td  rowspan="2">Forwarding Label (WTS will use the Forwarding Label instead of the WTS Label. Use 1 to use the forwarding label or set it to 0 or blank)</td><td colspan="4">ForwardingLabel</td><td rowspan="2">No</td>
      </tr>
    </table>

@@ Line 105: / Line 105: @@
      </tr>
      <tr>
-         <td rowspan="2">Recipient Room</td><td colspan="4">Room</td><td rowspan="2">No</td>
+         <td >Recipient Room</td><td colspan="4">AltRoom</td><td>No</td>
      </tr>
      <tr>
          <td colspan="4">Office</td>

@@ Line 3: / Line 3: @@
 Data can be imported into WTS as either part of your account's initial set-up or as part of a recurring administrative task to keep data synchronized with a back-end system.
-All Imports are handled via CSV (Comma Separated Values) file.
+All Imports are handled via a CSV (Comma Separated Values) file.
 Importing Recipients
@@ Line 10: / Line 10: @@
 There should be the same number of columns throughout the file as mentioned in the header.
-The Data is mapped as follows.
+The Data is mapped as follows:
-(Where there are multiple Accepted fields, they will be concatenated and comma delimited in the order shown here,
+(Where there are multiple Accepted fields, they will be concatenated and comma delimited in the order shown here.)
 <table width="80%" border="1" cellspacing="0" cellpadding="4px">

@@ Line 99: / Line 99: @@
      </tr>
 <tr>
-         <td >Send SMS - Allows fine tuning of SMS system per recipient. (Only used if Cell phone is provided. If Send SMS field is not included in the file, SQBX Defaults to 1.)</td><td colspan="4">SendSMS</td><td>No</td>
+         <td >Send SMS - Allows fine tuning of SMS system per recipient. (Only used if Cell phone is provided. If Send SMS field is not included in the file, WTS Defaults to 1.)</td><td colspan="4">SendSMS</td><td>No</td>
      </tr>
      <tr>
@@ Line 135: / Line 135: @@
      </tr>
 <tr>
-         <td >Send Email- Allows fine tuning of Email system per recipient. (Only used if Email Address is provided. If Send Email field is not included in the file, SQBX Defaults to 1.)</td><td colspan="4">SendEmail</td><td>No</td>
+         <td >Send Email- Allows fine tuning of Email system per recipient. (Only used if Email Address is provided. If Send Email field is not included in the file, WTS Defaults to 1.)</td><td colspan="4">SendEmail</td><td>No</td>
      </tr>
      <tr>
@@ Line 176: / Line 176: @@
-The '''Location Code''' is used to find locations previously imported or added into the SQBX system.
+The '''Location Code''' is used to find locations previously imported or added into the WTS system.
 In most cases, the location list will have been massaged into a very useful tree structure and the recipients lovingly placed in their correct locations.

@@ Line 1: / Line 1: @@
 == Importing Data ==
-Data can be imported into SQBX as either part of your account's initial set-up or as part of a recurring administrative task to keep data synchronized with a back-end system.
+Data can be imported into WTS as either part of your account's initial set-up or as part of a recurring administrative task to keep data synchronized with a back-end system.
 All Imports are handled via CSV (Comma Separated Values) file.
@@ Line 17: / Line 17: @@
      <tr>
-         <th width="30%">SQBX Field</th><th colspan = "4">Accepted Fields</th><th width="10%">Mandatory</th>
+         <th width="30%">WTS Field</th><th colspan = "4">Accepted Fields</th><th width="10%">Mandatory</th>
      </tr>