...
In case you want to associate a contact to a criteria or structure type. Follow these links: Define criteria's for the contacts and Define type of structure to create the records.
Examples
| Attachments |
|---|
Global fields
...
| Field code | Field type | Mandatory | Description | ||||
|---|---|---|---|---|---|---|---|
| CONTACT_NR | Text 20 | The field CONTACT_NR is mandatory for all OPERATION that is not INSERT. | Contact number. If your contact numbers have leading zeros, they must also be given, as they will be kept; the contact number is stored as a text. To be able to import existing contact numbers, the sequence for contact numbers must be adapted to generate numbers high than the highest imported contact number so that new contacts do not get an existing value. This is to be handled outside the import file. | ||||
| TITLE | Text 200 | Data will be imported if value is defined. Complete list for a specific institution can be found in screen Institution context → Initialization → List of Values → Individual Title. Standard values are: MR, MRS, MISS, MR_AND_MRS, UNDEFINED. | |||||
| 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 1000 | The function of the contact (Head of operations, Chairman, ...) | |||||
| REMARK | Text 2000 | Free remark. Adding two pipes « |
...
| 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 | |||||||
|---|---|---|---|---|---|---|---|---|---|---|
| OFFICIAL_NAME | Text 100 | Official name of the structure. The name will be truncated if it is too long. | ||||||||
| ADDRESS_NAME1 | Text 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_NAME2 | Text 38 | |||||||||
| STRUCT_TYPE | Code | The type of the structure. The code must be defined as described in Define type of structure | ||||||||
| COMMUNITY_TYPE | Code | The code of the community type. If it is left empty, then the structure isn't member of any community. | ||||||||
| ADMIN_NUMBER | CodeValue | 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.
Example
| ||||||||
| NB_EMPLOYEES | Number | |||||||||
| WEB_SITE | Text 255 | URL to the structure's website. It must contain the http:// prefix. |
...
| 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 | Address lines. | ||
| LINE2 | Text 100 | |||
| LINE3 | Text 100 | |||
| ZIPCODE | Text 10 | |||
| TOWN | Text 20 | |||
| TOWN_COMPLEMENT | Text 20 | |||
| COUNTRY | Code | 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. |
...
| Field code | Field type | Mandatory | Description | ||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TELEPHONE | Text 15 | 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
: | |||||||||||||||||||||||||||||||||||||||
| FAX | Text 15 | Fax number. Same rules as for PHONE. | |||||||||||||||||||||||||||||||||||||||
| CELLPHONE | Text 15 | Mobile phone. Same rules as for PHONE. | |||||||||||||||||||||||||||||||||||||||
| EMAIL1 | Text 250 | Will be used as username for ticket shop login. If email does already exist in the database, the email is imported for the contact but can't be used to login. There no possibility to import a list of passwords. Each new contact will need to request a password change (click on Have you forgotten your password ?) 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. |
...
| Field code | Field type | Mandatory | Description | |
|---|---|---|---|---|
| AUTH_CNIL_O | Boolean | Accept communications from institution | ||
| AUTH_PARTNER | Boolean | Accept communications from partners | ||
| AUTH_CNIL_T | Boolean | Accept transmission of electronic coordinates to third parties | ||
| AUTH_SMS_MMS | Boolean | Accept 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 | The code must be created as described in Define criteria's for the contacts.
Examples:
| ||||||||||||
| ... | ||||||||||||||
| CRIT50 | CodeValue |