...
| Field code | Field type | Mandatory | Description |
|---|---|---|---|
| INSTITUTION | Text 15 | Yes | Institution code owning the data to be imported. |
| ORGANIZATION | Text 15 | Yes Default: | Organization owning the data to be imported. A "« |
| OPERATION | Enum | Yes | 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.
INVALIDATE: Applicable to contact which has no sales.
ANONYMIZE: Applicable to all contacts (even if it has sales).
DROP : Should only be used for mis-import. Applicable to contact that imported and has no modified since then.
|
...
| 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, it 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 | ||
| REMARK | Text 2000 |
Individual
| Field code | Field type | Mandatory | Description | ||||
|---|---|---|---|---|---|---|---|
| FIRSTNAME | Text 100 | First name of the individual | |||||
| LASTNAME | Text 100 | Last name of the individual | |||||
| BIRTHDATE | Date | Birth date | |||||
| PREF_LANG | Code | Preferred language. Use the 2 lettre ISO code. Examples Language code Ex: en, fr, es, it, ... | PHOTO_PATH | Text 2000 |
Structure
| Field code | Field type | Mandatory | Description |
|---|---|---|---|
| STRUCTOFFICIAL_NAME | Text 100 | Structure name Data Official name of the structure. The name will be truncate if length > 100truncated if it is too long. | |
| ADDRESS_NAME1 | Text 38 | Taken from structure name if not defined (first 38 characters) | 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 | Taken from structure name if not defined (next 38 characters). | |
| STRUCT_CODETYPE | CodeValueCode | Must be predefined in system See reference page The type of the structure. The code must be defined as described in Structure type definition | |
| 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. | |
| NB_EMPLOYEES | Number | ||
| WEB_SITE | Text 2000 | Http hyperlink | URL to the structure's website. It must contain the http:// prefix. |
Address
| 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. | |
| LINE2 | Text 100 | ||
| LINE3 | Text 100 | ||
| ZIPCODE | Text 10 | ||
| TOWN | Text 20 | ||
| TOWN_COMPLEMENT | Text 20 | ||
| COUNTRY | Code | Country code Ex: FR, ES, EN, GB.... |
...