...
Field code | Field type | Mandatory | Description |
---|---|---|---|
CONTACT_NR | Text 20 | Yes 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. |
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 200 | Data will be imported if value is defined. | |
LETTER_SALUTATION | Text 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_SALUTATION | Text 200 | ||
FUNCTION | Text | ||
REMARK | Text | Free remark. Adding two pipes « |
Individual
Field code | Field type | Mandatory | Description |
---|---|---|---|
FIRSTNAME | Text 100 | First name | |
LASTNAME | Text 100 | Last name | |
BIRTHDATE | Date | Birth date | |
PREF_LANG | Code | Preferred language. Use the 2 lettre ISO code. Examples: en, fr, es, it, ... |
...
Field code | Field type | Mandatory | Description |
---|---|---|---|
ADDR_TYPE | Text 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. | |
LINE1 | Text 100 | Anything. Customer responsible for correct data Address lines. | |
LINE2 | Text 100 | ||
LINE3 | Text 100 | ||
ZIPCODE | Text 10 | ||
TOWN | Text 20 | ||
TOWN_COMPLEMENT | Text 20 | ||
COUNTRY | Code | Country code Exusing 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. |
Communication means
Field code | Field type | Mandatory | Description | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
TELEPHONE | Text 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:
Result:
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
: | |||||||||||||||||||||||||||||||||
FAX | Text 15 | Fax number. Same rules as for PHONE. | |||||||||||||||||||||||||||||||||
CELLPHONE | Text 15 | Mobile phoneEx: 06 88 48 87 10, (33)0677744594... Same rules as for PHONE. | |||||||||||||||||||||||||||||||||
EMAIL1 | Text 250 | Will be used as username for ticket shop login. If email is does already existedexist, 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+_-]+)+$ | |||||||||||||||||||||||||||||||||
EMAIL2 | Text 250 | Alternative email address. Cannot be used for login. | |||||||||||||||||||||||||||||||||
EMAIL3 | Text 250 | Alternative email address. Cannot be used for login. |
Authorization
Field code | Field type | Mandatory | Description |
---|---|---|---|
AUTH_CNIL_O | Boolean | Accept communication communications from institution | |
AUTH_PARTNER | Boolean | Accept communication communications from one partnerpartners | |
AUTH_CNIL_T | Boolean | Accepts Accept transmission of elec. electronic coordinates to third parties | |
AUTH_SMS_MMS | Boolean | Accept sms/mms SMS or MMS from institution | |
AUTH_LETTER | Boolean | Accept letter from institution | |
AUTH_PHONE | Boolean | Accept phone from institution | |
AUTH_EMAIL | Boolean | Accept email from institution |
...
Field code | Field type | Mandatory | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
CRIT01 | CodeValue | Formula: CritCode=CritValue1|CritValue2|CritValue3 Special case: If we use CONFIG row which mean:
Must be predefined in Contact criteria definitionThe code must be created as described in Contact criteria definition.
Examples:
| |||||||||
... | |||||||||||
CRIT50 | CodeValue |