Index

When adding a new info area or link, indices are generated automatically.

You can define additional indices for the most commonly used search processes.

Note: Only add index fields that you require. A large number of index fields impact negatively on performance, e.g. when searching.

The Index column displays the number of indices defined for the info area.

  1. Click on the Index column to display/edit/add indices:

    The primary index is highlighted in gray and cannot be changed.

    • No.: The number of the index is assigned automatically.
    • ID: The ID is automatically assigned. IDs 0-99 are used by the default data model, IDs starting from 100 are assigned depending on the user group and/or station number, see Number Ranges in Aurea CRM.
    • Properties: The index properties:
      • [ID] indicates the primary index. This is the index highlighted in gray.
      • [DUPLICATE] indicates the index is not unique; i.e. several records could contain identical values in the index fields. Click in this column for generated indices to enable the [DUPLICATE] property. If disabled, the index is unique.
      • [NOT NULL] indicates that empty values is not saved. Example: If the Synonym index for FI is used, companies, where no Synonym is entered, are not part of the search result.
    • Fields: The fields forming the index.
  2. To add a new index, double-click in the first empty row. A list of the fields of the info area is displayed. Select the first index field. Click on the Properties cell to specify the index' properties (s. above). Add more index fields by clicking on the Fields cell (s. below).

    To edit an existing index:

    • Edit custom indices by clicking in the Fields column.
    • Extend predefined indices (except primary indices) by adding Additional index fields.

    Note: Additional index fields are ignored by the business logic and when executing triggers.
  3. To add an index field:
    1. Click on the Fields cell (of a custom index).
    2. Click on the first empty row.
    3. Select a field.
    4. For text fields you can define the following properties:
      • Properties:

        UPPER: Adds the index in upper case (and therefore does not distinguish between upper or lower case).

        CASE: Adds the index with the field value and distinguishes between upper and lower case for that field.

        ALPHA: Removes all characters apart from letters and digits (e.g. spaces, special characters) and saves the result in a new field (<field name>_GEN_A). A database index is added, accessing this field.

        Note: Core Alpha Index only works with CRM.Win client. It does not work with CRM.Web. Furthermore, there is no configurable alphanumeric search in CRM, only a phonetic search. The phonetic search also allows searches for other fields and other info areas.

        PHONETIC: Adds a phonetic index in a new field (<field name>_GEN_P). Use this option to define a phonetic search index for Aurea CRM web. (The phonetic search fields are fixed in Aurea CRM win.) For a description of the algorithm used by the phonetic search, see Phonetic Search in the Business Logic Manual.

        Note: If a text field is already used in an index where the ALPHA or PHONETIC options have been enabled, the same field length must be used by this field in all other indices using the ALPHA or PHONETIC options.

        To search phonetically in KP you need to define the phonetic index in PE or CP. This phonetic index is then automatically used for KP as well if a field is searched that is mapped to a field with a phonetic index in PE or CP.

      • Length: Enter the number of characters to be used by the index. If undefined, the entire field value is used.
      • Binary-Sort: If checked, the sorting definitions defined in the mmdb.ini file (COLLATION (MS SQL) or MM_NLS_SORT (Oracle)) are ignored.
    5. For field of any type you can check the Not Null cell, i.e. if the field contains no value the record is not a part of the search result.
  4. To add an additional index field:
    1. Click on the Additional index fields cell.
    2. Click on the Fields cell.
    3. Select a field.
    4. The field is added with property [ADD].
    5. The Not in Key flag is automatically set. This means that the field is added to the index as "included column", i.e. the field does not affect the sorting and uniqueness of the index. Remove the flag to change this behavior.
      Note: The Not in Key option is not supported by Oracle databases.