Contact import format rules

Contact import format rules

INSTITUTION

ORGANIZATION

OPERATION

Acceptable values: CONFIG, INSERT, UPDATE.

It’s mandatory. So, the default value will be INSERT if empty.

Operation to be executed

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.

INSERT : Insert the row as a new contact (Individual / Relay / Structure).

UPDATE : Update the contact. Can be used to link criterion to contact.

CONTACT_NR

It must be unique.

It doesn’t exist in STX yet.

If contact numbers have leading zeros, they must also be given, as they will be kept; the contact number is stored as a text.

It contains digits only. Alphabet letters haven’t been supported yet.

Special characters such as underscores, periods, dashes don’t allow.

It’s mandatory. So, if it’s empty (don’t give any numbers), it will be provided while importing with import rules.

TITLE

Data will be imported if value is defined. Complete list for a specific institution can be found in screen Institution context → Initialisation → Pre-parameter → List of Values → Individual → Title. Use code and remove CONTACT_TITLE/ when input data file.

image-20250630-161643.png

 

Standard values are: MR, MRS, MISS, MR_AND_MRS, UNDEFINED.

It’s mandatory. So, the default value will be UNDEFINED if empty.

image-20250630-161107.png


LETTER_SALUTATION
ADDR_SALUTATION
FUNCTION
REMARK
FIRSTNAME
LASTNAME

BIRTHDATE

Format: dd.mm.yyyy or dd/mm/yyyy or dd-mm-yyyy

It must be a valid date. Wrong dates: 32.01.1999, 30.02.1999, 31.04.1999, 01.13.1999.

It must not in future.

Birthdate won’t be imported if wrong format / invalid date / in future.


PREF_LANG
OFFICIAL_NAME
ADDRESS_NAME1
ADDRESS_NAME2
STRUCT_TYPE
COMMUNITY_TYPE
ADMIN_NUMBER
NB_EMPLOYEES
WEB_SITE
ADDR_TYPE
LINE1
LINE2
LINE3
ZIPCODE
TOWN
TOWN_COMPLEMENT
DEPARTMENT

COUNTRY

Country code using the ISO codes. Example: FR, ES, EN, GB (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.

TELEPHONE, TELEPHONE2, TELEPHONE3, FAX and CELLPHONE

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.

The national prefix (0 for CH, FR, 1 for US, 9 for ES, etc. see COUNTRY table) will be automatically removed in the database if present in the input number.

Input COUNTRY

Input number

Stored as

Remark

Input COUNTRY

Input number

Stored as

Remark

FR

01 40 15 80 00

33 / 140158000

The leading 0 (national prefix) has been removed for France

FR

1 40 15 80 00

33 / 140158000

 

FR

0041 21 613 21 11

33 / 041216132111

Country prefix (41 but looking for 33) could not be recognized
One leading 0 (national prefix) has been removed for France

CH

0041 21 613 21 11

+41 21 613 21 11

41 / 216132111

Country prefix could be recognized

FR

(41)216132111
(41)0216132111

41 / 216132111

This format allows to force the country code.
This is the preferred format for import, as it lets you choose the country prefix independently from the country of residence.

FR

01 SVP 77 77

017777

 

IT

(39)0444 651070

39 / 0444 651070

Keep the “0” in telephone numbers for Italy.

EMAIL1

Format rule: local part + “@” + domain part (consist of domain name and top-level domain)

Allowed characters: alphabet letters (a–z) and digits (0–9) and some special characters such as underscores, periods, dashes.

Special characters cannot be the first or last character in the local part or in domain part, and they cannot appear consecutively.

ASCII characters only.

Lower cases only.

Invalid email

Valid email

Invalid email

Valid email

USERNAME01@SECUTIX.COM

USERNAME01@secutix.com

username01@SECUTIX.COM

username01@SECUTIX.com

Username01@Secutix.Com

username01@secutix.com

user..name01@secutix.com

.username01@secutix.com

username01.@secutix.com

user.name01@.secutix.com

user.name01@secutix.com.

user.name01@secutix..com

user.name01@secutix.com

Set EMAI

Internet account will be automatically created for EMAIL1 while importing without sending any emails to end users. The customer should comment if they don’t want to create internet account for those contacts.

EMAIL1 won’t be verified while importing. The customer should comment if they want to verify those emails.

Email will be changed to domain @blackhole.secutix.com when it’s pre-production. For example: username@secutix.com will be username$secutix.com@blackhole.secutix.com

image-20250630-153543.png
image-20250630-153742.png

EMAIL2 and EMAIL3

Same rule as EMAIL1, except internet account and verification.

All columns of AUTH_*

Acceptable values:

T/TRUE/True will be T.

F/FALSE/False will be F.

All columns of CRIT*

image-20250630-150222.png

 

Only 1 line of configuration with OPERATION = CONFIG and CRIT columns contain criterion code. Other lines for import with OPERATION = INSERT will contain criterion values. It can be single value or multiple value or boolean (same rule as AUTH_*).

Lines with a pair of criterion code and single value (example 2)/multiple value (example 3)/boolean (same rule as AUTH_*).