Aurea CRM Field Types

Boolean field

y/n

B

---

Text field

text

C

---

mandatory: Length (see Length)

optional: Properties (see Properties), Mask (see Mask)

Telephone field

text

C

If CRM.phone is installed, clicking a number starts dialling. Phone fields are defined in the data model (Telephone column), see Telephone.

---

E-Mail field

text

C

If the "E-Mail" property is set in the data model, e-mail addresses are displayed as a hyperlink: Clicking the address opens the mail client.

---

Hyperlink field

text

C

If the "Hyperlink" property is set in the data model, web addresses are displayed as a hyperlink: Clicking the address opens the web page.

---

Rep fields

uid, reference (uid)

Z,L

Consists of four fields, e.g. Rep (Z) | Rep ID (L) | Rep Group (Z) | Rep Group ID (L)

If a user enters a rep's ID in the Rep ID field, the Rep, Rep Group ID and Rep Group fields are filled in automatically.

---

optional (for uid): Properties (see Properties)

Catalog field

fix catalog

X

Field referencing a fixed catalog

---

mandatory: Catalog (see Catalog)

Catalog field

var catalog

K

Field referencing a variable catalog

---

mandatory Catalog

Date field

date (4Byte)

D

Date field (without time)

---

optional: Mask (see Mask)

Time field

time (hh:mm)

T

Time field with hours and minutes

---

Time field

time (hh:mm:ss)

T

Time field with hours, minutes and seconds

---

Time field

time (hh:mm:ss,ttt)

T

Time field with hours, minutes,seconds and milliseconds

---

Combined date/time field

date, time (hh:mm)

D,T

Consists of two fields (Date and Time)

Use these fields to represent time zones.

Use mmba.exe –-writeDateTime to output a list of all combined date and time fields, seemmba.exe Parameters .

---

Combined date/time field

date, time (hh:mm:ss)

D,T

---

Combined date/time field

date, time (hh:mm:ss,ttt)

D,T

---

Number field

small int (1 Byte)

S

Integer between 0 and 255

---

optional: Format (see Format), Mask (see Mask)

Number field

short int (2 Byte)

S

Integer between 0 and 65535

---

optional: Format, Mask

Number field

signed int (4 Byte)

L

Integer between -2147483647 and +2147483647

---

optional: Format, Mask

Number field

int (4 Byte

L

Integer between 0 and 2147483647

---

optional: Format, Mask

Number field

long int (8 Byte)

L

Integer between 0 and 99999999999999999 (17 places)

---

optional: Format, Mask

Number field

decimal (4 Byte)

F

Floating point number

---

optional: Format, Mask

Number field

decimal (8 Byte)

F

Double-length floating point number

---

optional: Format, Mask

Binary field

binary

Field containing binary data

Binary data can only be entered and read via add-on programming.

---

mandatory: Length (see Length)

Station number field

sno (2 Byte)

S

Field containing a station number

---

optional: Format (see Format)

Serial number field

lno (4 Byte)

L

Field containing a serial number

---

optional: Format

Naming convention for station/serial number fields:

• <InfoAreaId>-StaNo / <InfoAreaId>-SerNo: Station and serial number fields representing the unique key of a record. <InfoAreaId> is the info area ID of the current record, e.g. FI-StaNo and FI-SerNo for company records.
• <InfoAreaId>_StaNo / <InfoAreaId>_SerNo: Station and serial number fields representing a link to another record. <InfoAreaId> is the info area ID of the linked record. If more than one link to the same info area exists, the fields are numbered, e.g. FI_1_StaNo, FI_2_StaNo etc.

Tenant number field

mno (4 Byte)

L

Tenant number field: An integer field used to store the tenant number, see Tenants.

Naming convention: <InfoAreaId>-TenNo, e.g. FI-TenNo.

Only one field of this type is permitted per info area.

4003

Currency field

currency

K

Stores the currency used for the record.

This field accesses the Currency catalog.

Only one field of this type is permitted per info area.

4005

External key fields

ext.key

K,C

Consists of two fields: Ext. System (K, 4017) | Ext. Key (C, 4018)

This field type is available in all info areas whose key consists of station number plus serial number and for all info areas whose key consists of a numeric field (e.g. the Rep info area).

The Company, Person and Property info areas have external key fields by default.

The external key can be used when importing, see Importing with External Keys in the Aurea CRM win Administrator Guide.

4017, 4018

Hierarchy code field

hierarchy code

C

Only available in info areas with at least one rep field.

The field stores a rep's hierarchy code.

If a rep is entered in the rep field, the rep's hierarchy code is automatically entered in the corresponding hierarchy code field.

Read-only by default - can be changed, see Properties.

External match-up fields

ext.matchup

Z

Consists of three decoded fields (Score, Text, Description) used to match up data using an external application, see External Match-up.

Aurea CRM copies the values from the node in the external XML file as follows:

Score (match-up) (4019): The score that indicates how similar the records are ("Score" node).

Text (match-up) (4020): Contents of the "Text" node.

Description (match-up) (4021): Contents of the "Description" node.

4019-21

Geographic coordinates field

geographic coordinates

F,X,L

Select this type to save geographic coordinates for a record. The following fields are created:

x (geographic coordinate): Latitude (decimal(8Byte))

y (geographic coordinate): Longitude (decimal(8Byte))

Precision (Geo-coordinates): fixed catalog defining the quality of the geocoding: empty (default), Manual input, High, Medium, Low, failed.

Updated (Geo-coordinates): Date and time of creation or last update of the coordinates (long int(8Byte))

The out-of-the-box data model contains these fields for ID, FI, KP, ZA, OJ (BTB only) and PE.

To use geographic coordinates in variable queries (using the location of the current rep or station as a comparison value), use the geographic coordinate fields in the Rep info area (ID) and/or define geographic coordinate fields in the Station info area (AS).

If you are using MS SQL, an additional field (type: "geography", name: "XY_F<Field number>") is created in the database.

If an index is defined for the longitude and latitude fields and the "geography" data type is supported, a spatial index is only added for this field.For information on the interface with external applications, see Geo-Coordinates.

HTML field

html-text

C

Select this type to add a field for storing formatted text in the database, e.g. when importing e-mails into Aurea CRM or when creating html-formatted text in Aurea CRM web (e.g. for e-mail activities).

To create an HTML field:

Create a new field of type "html-text".

Select an existing text field to which the HTML field is linked.

When adding text to the HTML field, the plain text (without html tags) is automatically entered into the linked text field. Line breaks are preserved in the plain text field.

Make sure that only one of the fields - either HTML or text - is editable for the user. Otherwise the field contents may no longer be synchronized correctly:

If the plain text field is edited, changes are transferred to the HTML field.

If the HTML field is edited in a way that the field content no longer starts with a <PRE> tag, changes in the plain text field are no longer transferred to the HTML field.

mandatory: Length (see Length)

If you linked the html field to a text field, the text field's length is used.

2nd currency field

virtual(2nd currency)

Z

Stores values of a record in the 2nd currency, see Currencies in the Business Logic Manual.

This field type is only available, if a field of type "currency" and a numeric field (small int, short int, signed int, int, long int, decimal) with the "Currency" property checked in the Properties column exists.

The 2nd currency field's name is automatically generated as "<field name> (2C)". Changing the label of the linked numeric field changes the label of the 2nd currency field as well.

Corporate currency field

corporate currency

F,K,D

Stores values of a record in the corporate currency.

To create a corporate currency field:

Define a Z5 variable update_CorporateCurrency (for info area Exchange Rate (BTB/FS: WK, OTC: WT), field Currency).

Define the corporate currency as variable value, i.e. value of the "Currency" catalog.

In the data model, create a new field of type "corporate currency".

Select the field whose value should be converted.

The following fields are created:

4024 (Currency): A catalog field containing the currency defined in the Z5 variable.

4025 (Rate): The exchange rate as defined in WT or entered manually.

4026 (Date): The date of the most recently entered exchange rate.

the actual corporate currency field displaying the value of the reference field converted to the corporate currency.

For detailed information on the business logic, see Currencies in the Business Logic Manual.

4024-26

Properties (see Properties)

Reference field

reference (field)

Z

Contains a field value transferred from another info area.

---

Link field

reference (table)

Z

Contains the link to another record.

The actual link consists of key fields (e.g. sno, lno) plus one field of type "reference (table)", e.g the link to a Ticket (KM) record in the Activity (MA) info area.

The list contains one entry per info area and link.

Select the desired entry and confirm with OK.

The fields in the selected info area are then listed in a new window. Select the field whose contents should be transferred and confirm with OK.

---

System fields

<various>

<various>

Fields that track when a record was added, edited or communicated, when, on which station and by whom, see System Fields in the Aurea CRM win Administrator Guide.

>=4000

Custom fields

---

---

Fields defined in CustomFields.xml.