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 code

Field type

Mandatory

Description

INSTIT

Text 15

Yes

Institution code owning the data to be imported.

ORGANIZATION

Text 15

Yes

Organization owning the data to be imported.

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

OPERATION

Enum

Yes

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 code	Field type	Mandatory	Description
CONTACT_NR	Text 20	Yes if OPERATION is not INSER	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.
ROLE	Enum		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.
TITLE	Text 20		Data will be imported if value is defined. If value is empty, it will be taken from other field.
LETTER SALUTATION	Text 20
ADDRESS SALUTATION	Text 20
FUNCTION	Text 20
REMARK	Text 2000

Individual

Field code	Field type	Description
FIRSTNAME	Text	First name of the individual
LASTNAME	Text	Last name of the individual
BIRTHDATE	Date	Birth date
PREFERRED LANGUAGE	Text 2	Filled with country code
PHOTO PATH	Text

Structure

Field code	Field type	Description
STRUCTURE NAME	Text 100	Data will be truncate if length > 100.
ADDRESS NAME 1	Text 38	Taken from structure name if not defined (first 38 characters)
ADDRESS NAME 2	Text 38	Taken from structure name if not defined (next 38 characters).
STRUCTURE CODE	Text 8
COMMUNITY TYPE
ADMIN NUMBER
NB EMPLOYEES
WEBSITE

Address

Field code	Field type	Description
ADDRESS TYPE	Text 3	M: Main address S: Shipment address B: Billing address Leave empty --> that address use for 3 types.
LINE 1	Text	TBD with max length
LINE 2	Text
LINE 3	Text
ZIPCODE	Text
TOWN	Text
TOWN COMPLEMENT
COUNTRY	Text 2	Country code (TBD: table mapping for referenced)

Communication mean

Field code	Field type	Description
PHONE 1	Text 13	Landline phone number. TBD: phone format.
PHONE 2	Text 13	Landline phone number. TBD: phone format.
PHONE 3	Text 13	Landline phone number. TBD: phone format.
FAX	Text 10
CELLPHONE	Text 13	Mobile phone
EMAIL 1	Text 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 2	Text 50
EMAIL 3	Text 50

Authorization

Field code	Field type	Description
CNIL_O	Boolean	TDB: mean?
PARTNER	Boolean
CNIL_T	Boolean
SMS_MMS	Boolean
LETTER	Boolean
PHONE	Boolean
EMAIL	Boolean

Criterion