You can use any of the special fields below when you do your import process. They will match up with fields in the database such as lookup data or phone numbers.

The import routines will automatically create new values into Code Tables for the special meaning fields during the import process. In most cases, there is no need to prepopulate code table values that will be used. The exception is gPaymentMethod - all payment methods must be created prior to using them.

• gPatronType - patron type - individual, company, staff, etc. Code Table "Patron Type".

• gPhoneHome - patron home phone number
• gPhoneWork - patron work phone number
• gPhoneCell - patron mobile phone number
• gPhoneFax - patron fax phone number
• gEmailHome - patron home email address
• gEmailWork - patron work email address
• gWebsite - patron work website URL

Some special fields that will "update" the field, rather then add new contact information to the patron account

• gPrimaryPhone - Patron primary phone number
• gPrimaryEmail - Patron primary email address
• gPrimaryFax - Patron primary fax number
• gPrimaryWeb - Patron primary web site URL

• MKT_C_SEQ - REFER to special field for matching patron numbers on import
• gC_AGE_CODEresult - Marketing age code
• gC_MKT6result - Marketing field #6
• gC_MKT7result - Marketing field #7
• gC_MKT8result - Marketing field #8

• gC_ACTIVEresult - Marketing Volunteer Status
• gMktVol1Result - Volunteer Popup field #1
• gMktVol2Result - Volunteer Popup field #2
• gMktVol3Result - Volunteer Popup field #3
• gMktVol4Result - Volunteer Popup field #4
• gMktVol5Result - Volunteer Popup field #5
• gMktVol6Result - Volunteer Popup field #6
• gMktVol7Result - Volunteer Popup field #7
• gMktVol8Result - Volunteer Popup field #8
• gMktVol9Result - Volunteer Popup field #9
• gMktVol10Result - Volunteer Popup field #10

• gDonorGivingCapacity - Marketing Donor Giving Capacity
• gDonorMovesStatus - Marketing Donor Moves Management Status

• PM_SHORT_NAME and gName1 through gName15 - are up to 16 mail list columns. If you want to import any mail list, then you must have ONE column called PM_SHORT_NAME.
  • The contents of the field indicate which mail list to which the patron will be added.
  • You can comma separate the mail lists to add to a patron such as list1,list2,list3 and/or
  • You can have multiple columns in your import file named 'gName1' through 'gName15'. In those columns, you can have blanks or mail lists to which you want people added (eg list1 or list2, etc.)
  • In this way, you can use up to 16 columns to specify a lot of mail lists to add a patron to, either many in one column separated by commas, or in separate columns if that is more clear for you.

• I_ORD_REASON_BUY_RESULT - Order reason "Why did Patron Buy?", Code Table "Order Reason to Buy".
• gSource - Delivery Method - ticket handling status.
  • 0 = Hold for Pickup/Taken
  • 1 = Mail to Patron
  • 2 = Hold for WillCall
  • 3 = Hold @ Door for Coupon

• gTixUsed - Patron Attended - flag to indicate if patron attended the performance.
  • attended = indicate that patron attended the performance
• gAttendedReason - description for the Patron Attended or Not Attended Reason. Code Table "Course Attendance Reasons".

• gDonor1Field - Donor Popup field #1
• gDonor2Field - Donor Popup field #2
• gDonor3Field - Donor Popup field #3

• gAccount - Account number to assign to new donation campaigns

• gMember1Field - Member Popup field #1
• gMember2Field - Member Popup field #2
• gMember3Field - Member Popup field #3

• gAccount - Account number to assign to new member/pass type

• gPaymentMethod - Payment Method. Matching "Payment Code" in code table "Payment Methods". All payment methods must be created prior to using them.
• gOrigin - Payment Source - location of where the payment originated.
  • 0 = Internet/Web Sales
  • 1 = Telephone Order
  • 2 = Mail Order
  • 3 = Patron Present

The following fields could be used as unique identifiers to import and match records to data that exists in Theatre Manager, or they could just be used to import data. The meaning changes depending on how you use them for matching data during the import process.

MKT_C_SEQ

This is a special field that is allows you to match imported data with existing patrons based on the patron number. This should only be used if the data file originated from Theatre Manager in the first place, such as for address correction, and you are sure the Patron number matches the one in Theatre Manager (otherwise the results will be overwritten and jumbled data). If you are going to match on patron number, be sure to make a backup of the database first and verify the success of the results after the import.

If you plan to Export patron names for address correction purposes through a Mail House or other verification service, be sure to include the Patron number on the export, so that when you reimport the corrections back in, you have the patron number to link the corrected address with the correct patron record. In addition, be sure not to merge any patron records while the list is at the Mail House, or else the patron numbers may not align when you reimport the data.

Helpful Link: Canada Post address correction web site

MKT_FIELD_1 through MKT_FIELD_5

These are the marketing fields on the patron record. If they are unique within your database, and you specify them as a column header in the import file, they will also be presented as 'matching field' options. Only do this is you have used these fields to reference unique keys from another system (such as prior ticketing systems).