S-360 Documentation

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

File format for contacts

The generic file format is described in Generic file format (Extended). This documents describes all available import fields.

Global fields

Field codeField typeMandatoryDescription
INSTITText 15Yes

Institution code owning the data to be imported.

ORGANIZATIONText 15Yes

Organization owning the data to be imported.

A "*" indicates that all organizations of the given institution are concerned.

OPERATIONEnumYes

Operation to be executed

INSERT : insert the row as a new contact

UPDATE : update the contact. Can be used to link criterion to contact.

UPDATEACT: update the contact and reactivate it if needed.

DELETE: Delete the contact address, communication mean.

  • For authorization and criterion value. Only delete the value that specified in excel file.
  • The email will be empty and contact can't be login to ticketshop anymore.
  • This action is irreversible.

INVALIDATE: Applicable to contact which has no sales.

  • Just mark contact as invalid with reason: ACCOUNT_DELETED.
  • All other information are in tact (not removed).

ANONYMIZE: Applicable to all contacts (even if it has sales).

  • All contact information is deleted. Contact name is changed in to 'XXXXXXXX'.
  • Set contact as ACCOUNT_DELETED and remark contact with 'Contact anonymized'.
  • The contact's sales information are in tact (not removed).
  • This action is irreversible.

DROP : Should only be used for mis-import

  • Drop the contact and all its information. The contact is not dropped if it is used in existing sales.
  • The contact row is removed from system forever.

Contact

Field codeField typeMandatoryDescription
CONTACT_NRText 20Yes if OPERATION is not INSERT

Contact number. If your contact numbers have leading zeros, they must also be given.

Note: The field CONTACT_NR is mandatory for all OPERATION that is not INSERT.

ROLEEnum Role of the contact when it is created. If the field is left empty, RELAY will be used when Individual and structure data are given. PUBLIC when only individual or structure data is given.
TITLEText 20 

Data will be imported if value is defined.

If value is empty, it will be taken from other field.

LETTER SALUTATIONText 20 
ADDRESS SALUTATIONText 20 
FUNCTIONText 20  
REMARKText 2000  

Individual

Field codeField typeMandatoryDescription
FIRSTNAMEText 

First name of the individual

LASTNAMEText Last name of the individual
BIRTHDATEDate Birth date
PREFERRED LANGUAGEText 2 Filled with country code
PHOTO PATHText  

Structure

Field codeField typeMandatoryDescription
STRUCTURE NAMEText 100 

Data will be truncate if length > 100.

ADDRESS NAME 1Text 38 Taken from structure name if not defined (first 38 characters)
ADDRESS NAME 2Text 38 Taken from structure name if not defined (next 38 characters).
STRUCTURE CODEText 8  
COMMUNITY TYPE   
ADMIN NUMBER   
NB EMPLOYEES   
WEBSITE   

Address

Field codeField typeMandatoryDescription
ADDRESS TYPEText 3 

M: Main address

S: Shipment address

B: Billing address

Leave empty --> that address use for 3 types.

LINE 1Text TBD with max length
LINE 2Text  
LINE 3Text  
ZIPCODEText  
TOWNText  
TOWN COMPLEMENT   
COUNTRYText 2 Country code (TBD: table mapping for referenced)

Communication mean

Field codeField typeMandatoryDescription
PHONE 1Text 13 

Landline phone number.

TBD: phone format.

PHONE 2Text 13 

Landline phone number.

TBD: phone format.

PHONE 3Text 13 

Landline phone number.

TBD: phone format.

FAXText 10  
CELLPHONEText 13 Mobile phone
EMAIL 1Text 50 

Will be used as username for ticket shop login.

If data is already existed, the email is imported but can't be used to login.

The email validation are different from systems. It won't be imported if validation failed (standard email format will be ok, don't worry).

EMAIL 2Text 50  
EMAIL 3Text 50  
    
  • No labels