Institution code owning the data to be imported.

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.

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.

CONFIG: Configuration line for admin numbers and criteria.

• If the codes are defined on this row, then the fields can contain only the value instead of the CodeValue.
• The configuration remains valid until a new configuration line
• Initially, no codes are defined, forcing the CodeValue format.

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.

Data will be imported if value is defined.

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'.

Free remark.

Adding two pipes « || » at the beginning will add the text to an existing remark instead of overwriting it.

First name

Preferred language.

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

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

Name of the structure for the adresse

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

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

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.

• On the CONFIG row, the user can define the default code.

Example

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.

Address lines.

Country code using the ISO codes

Example: FR, ES, EN, GB (and not UK), ...

Full name of the country can also be given. They should be written exactly (spaces,hyphens, ...) as they are defined in SecuTix.

By default, the country of the institution is used.

Landline phone number.

Following formats will be recognized. These examples assume country FR (country of the address, or by default the country of the institution).

The initial << + >> sign will be recognized as well as 00.

The country prefix can be forced if it entered in parenthesis at the beginning.

All other non digit signs are ignored.

Examples

:

Mobile phone. Same rules as for PHONE.

Will be used as username for ticket shop login.

If email does already exist, 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+_-]+)+$

Alternative email address. Cannot be used for login.

Accept communications from institution

The code must be created as described in Contact criteria definition.

• Several values can be given. They need to be separated by pipes.
• On the CONFIG row, the user can define the default code.

Examples: