...
In case you want to associate a contact to a criteria or structure type. Follow these links: Define criteria’s 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 | Yes if OPERATION 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 fileNote: The field CONTACT_NR is mandatory for all OPERATION that is not INSERT. |
| 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 | The function of the contact (Head of operations, Chairman, ...) | |
| REMARK | Text | Free remark. Adding two pipes « |
...
| Field code | Field type | Mandatory | Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| CRIT01 | CodeValue | The code must be created as described in Define criteria’s criteria's for the contacts.
Examples:
| |||||||||
| ... | |||||||||||
| CRIT50 | CodeValue |