...
In case you want to associate a contact to a criteria or structure type. Follow these links: Contact criteria definition and Structure type definition Define criteria’s for the contacts and Define type of structure to create the records.
Examples
...
| 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 Structure Define type definitionof 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 2000 | URL to the structure's website. It must contain the http:// prefix. |
...
| 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 | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| CRIT01 | CodeValue | The code must be created as described in Contact criteria definition Define criteria’s for the contacts.
Examples:
| |||||||||
| ... | |||||||||||
| CRIT50 | CodeValue |