Application File Imports Release Notes Sync Web Services FAQ

New Loyalty Member w/ Points Available and Custom Fields File

Intended Application

To insert new members into the database with or without an initial available point balance, along with optional member custom field data.

 

Notes

  • Header record is expected.  The first record will be skipped.
  • If member custom fields are used, they must by represented by their external reference in the header, in the proper column position.
  • If custom field data is for a "list" type custom field, a semi-colon must be used to separate the items.
  • If an invalid parameter for a "dropdown" custom field is imported, any existing value for this field will be removed.
  • For checkbox value types; 1, Y, YES = True (Checked) || 0, NO, N = FALSE (Unchecked).
  • Any delimiter, except for a semi-colon and [tab], can be used to separate columns.  The delimiter used is then specified at the time of file import.
  • Records with Account Ids that already exist in the database will be ignored.
  • At the time of import, user must select a transaction type using the direct point entry method in order for points to be assigned to the member accounts.
  • In the event a provided birthdate can't be properly interpreted (bad data), the file import will suspend itself.

 

File Structure

DATA COLUMN

DATA TYPE DATA REQUIRED? FORMATTING NOTES

Account Id

Alphanumeric

No

 

 Data is not required, but is highly recommended.
Name Prefix Alphanumeric

No

 

 

First Name

Alphanumeric

Yes

   
Middle Name Alphanumeric No    
Last Name Alphanumeric Yes    
Name Suffix Alphanumeric No    
Birthdate Date/Time No YYYY-MM-DD  
Gender Alphanumeric No   Allowed Values (Blank, M, F, Male, Female)
Address Line 1 Alphanumeric No   This data must be included in order for all address components to be stored.
Address Line 2 Alphanumeric No    
Address Line 3 Alphanumeric No   Antiquated field -- data no longer stored.
City Alphanumeric No   This data must be included in order for all address components to be stored.
Region/State/Province Alphanumeric No   2-letter abbreviation or region name (dependent on region type for country).  This data must be included in order for all address components to be stored.
Postal/Zip Code Alphanumeric No   This data must be included in order for all address components to be stored.
Country Alphanumeric No   2-letter abbreviation.  This data must be included in order for all address components to be stored.
Phone Formatted Numeric No 1-(XXX)XXX-XXXX  
Email Address Alphanumeric No email@address.com  
Available Point Balance Decimal No    
Customer Web Portal Password Alphanumeric No   Maximum of 20 characters.
Kiosk PIN Numeric No   Maximum of 6 characters.
Member Custom Field(s) Varies No    

 

Sample File

In the file below, MemberType represents a member custom field.

1:
2:
AccountId|Prefix|Name|First|Middle|Last|Suffix|Birthdate|Gender|Add1|Add2|Add3|City|Region|PostalCode|Country|Phone|Email|PointAvail|Password|PIN|MemberType
34109||Jason|C|Smith||1984-11-11|M|100 Main St|APT 4||Newark|DE|19711|US|1(302)555-1212|jsmith@smartbutton.com|493.10|charlie|54321|A

Please note: All external ALP SaaS links and references are directed to US datacenter unless specifically noted.


Tags:
Home: Aimia Loyalty Platform SaaS Wiki
Copyright © 2003-2018 Smart Button, an Aimia Company. All rights reserved.
What's new: Recently changed articles