Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 35 Next »

File format for contacts

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

In general:

  • Field with empty data mean "ignore this field".
  • Put value '=' will remove the current value in system.
  • Field with data will be imported.

A contact can be Individual or Structure so for Contact creation case: At least FIRSTNAME, LASTNAME or STRUCT_NAME must have data.

In case you want to associate a contact to a criteria or structure type. Follow these links: Contact criteria definition and Structure type definition to create the records.

Global fields

Field codeField typeMandatoryDescription
INSTITUTIONText 15Yes

Institution code owning the data to be imported.

ORGANIZATIONText 15

Yes

Default: *

Organization owning the data to be imported.

A « * » indicates that all organizations of the given institution are concerned. This is the default value.

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: Applicable to all contacts.

  • 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. Applicable to contact that imported and has no modified since then.

  • Drop the contact and all its information.
  • The contact is not dropped if it is used in existing sales.

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 200 

Data will be imported if value is defined.

LETTER_SALUTATIONText 200 

If value is empty, these fields will be interpolated from the TITLE field, according to the language of the individual.

Ex: if TITLE = 'MR'

→ ADDR_SALUTATION = 'Dear Sir'

LETTER_SALUTATION = 'Mr'.

ADDR_SALUTATIONText 200 
FUNCTIONText  
REMARKText  

Individual

Field codeField typeMandatoryDescription
FIRSTNAMEText 100 

First name

LASTNAMEText 100 Last name
BIRTHDATEDate Birth date
PREF_LANGCode 

Preferred language.

Use the 2 lettre ISO code. Examples: en, fr, es, it, ...

Structure

Field codeField typeMandatoryDescription
OFFICIAL_NAMEText 100 

Official name of the structure. The name will be truncated if it is too long.

ADDRESS_NAME1Text 38 

Name of the structure for the adresse

If it is empty, it is taken from the official name

 If it is too long, it is truncated.
ADDRESS_NAME2Text 38 
STRUCT_TYPECode 

The type of the structure. The code must be defined as described in Structure type definition

COMMUNITY_TYPECode The code of the community type. If it is left empty, then the structure isn't member of any community.
ADMIN_NUMBERCodeValue Administrative number, for example a SIRET number. Only one number can be given here, but subsequent updates of the contact may help adding several numbers.
NB_EMPLOYEESNumber  
WEB_SITEText 2000 URL to the structure's website. It must contain the http:// prefix.

Address

Field codeField typeMandatoryDescription
ADDR_TYPEText 3 

M: Main address

S: Shipment address

B: Billing address

Ex: M or B or S or MB or MBS, etc...

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

LINE1Text 100 Anything. Customer responsible for correct data.




LINE2Text 100 
LINE3Text 100 
ZIPCODEText 10 
TOWNText 20 
TOWN_COMPLEMENTText 20 
COUNTRYCode Country code Ex: FR, ES, EN, GB....

Communication mean

Field codeField typeMandatoryDescription
TELEPHONEText 15 

Landline phone number. Follow standard format and international format.

Phone number is followed country code where customer located. That information is stored in institution data.

Example:

  • Customer is placed in Switzerland (CH).
  • The data in excel is: 01 40 15 80 00, 0169395090, (33)0134806517...

Result:

  • They're all in valid format and imported.
  • The first 2 are recognized as Swiss phone number.
  • But the last one is stored as France phone number.
FAXText 15  
CELLPHONEText 15 

Mobile phone

Ex: 06 88 48 87 10, (33)0677744594...

EMAIL1Text 250 

Will be used as username for ticket shop login.

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

The email validated by regular expression: ^[0-9a-z+\$_-]+(\.[0-9a-z+\$_-]+)*@[0-9a-z+_-]+(\.[0-9a-z+_-]+)+$

EMAIL2Text 250  
EMAIL3Text 250  

Authorization

Field codeField typeMandatoryDescription
AUTH_CNIL_OBoolean 

Accept communication from institution

AUTH_PARTNERBoolean Accept communication from one partner
AUTH_CNIL_TBoolean Accepts transmission of elec. coordinates to third parties
AUTH_SMS_MMSBoolean Accept sms/mms from institution
AUTH_LETTERBoolean Accept letter from institution
AUTH_PHONEBoolean Accept phone from institution
AUTH_EMAILBoolean Accept email from institution

Criterion

Field codeField typeMandatoryDescription
CRIT01CodeValue 

Formula: CritCode=CritValue1|CritValue2|CritValue3

Special case: If we use CONFIG row which mean:

  • CONFIG contains CritCode.
  • Contact row contains CritValue1|CritValue2|CritValue3.

Must be predefined in Contact criteria definition

...  
CRIT50CodeValue 
  • No labels