...
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
Global fields
Field code | Field type | Mandatory | Description |
---|
INSTITUTION | Text 15 | Yes | Institution code owning the data to be imported. |
ORGANIZATION | Text 8 | Yes Default: * | Organization owning the data to be imported. A « * » indicates that all organizations of the given institution are concerned. This is the default value. |
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. - Delete the contact address, communication mean
- For authorization and criterion value. Only delete the value that specified in excel file.
- The email will be empty and contact can't be login to ticketshop anymore.
- This action is irreversible.
INVALIDATE: Applicable to contact which has no sales. - Just mark contact as invalid with reason: ACCOUNT_DELETED.
- All other information are in tact (not removed).
ANONYMIZE: Applicable to all contacts (even if it has sales). - All contact information is deleted. Contact name is changed in to 'XXXXXXXX'.
- Set contact as ACCOUNT_DELETED and remark contact with 'Contact anonymized'.
- The contact's sales information are in tact (not removed).
- This action is irreversible.
DROP : Should only be used for mis-import. Applicable to contact that imported and has no modified since then. - Drop the contact and all its information.
- The contact is not dropped if it is used in existing sales.
CONFIG: Configuration line for admin numbers and criteria. - If the codes are defined on this row, then the fields can contain only the value instead of the CodeValue.
- The configuration remains valid until a new configuration line
- Initially, no codes are defined, forcing the CodeValue format.
|
...