Multi-language Sort

Aurea CRM supports unicode character sets and therefore the input of data using different codepages. Using multi-language sorts, each user can determine their own language-specific sort settings.

Types of Sort

  • Data is sorted by field
    • by selecting Data > Sort from the menu
    • by clicking on the column header in a list
    • in the dialog box used to select catalog values

    The sort order for text fields is based on the Windows regional settings (Start > Settings > Control Panel > Regional and Language Options).

    media/image237.png

  • Data is sorted by index
    • by selecting Data > Sort from the menu
    • when sorting in selections

    The sort order used for indices is defined in the index itself. The Oracle database parameter MM_NLS_SORT entered in the mmdb.ini file is used to construct the index. This allows all users to access the same sort independent of their regional settings.

In order to allow users of an Oracle database to use a language-specific sort order for indices, define the following sort order:

  1. Enter all the sort orders you require additionally in the mmdb.ini file. These need to be "Linguistic Sorts" defined by Oracle (>> Oracle documentation). The first value must always be present and is used as the default value.

    Example: Aurea CRM installation using a central database with users in three countries (Austria, the Czech Republic and Russia).

    [MM ORA]

    MM_NLS_SORT=BINARY,CZECH,RUSSIAN,GERMAN

    Note: Each new index impacts negatively on the performance of the database. Consider whether using a "Multilingual Linguistic Sort" would also meet your requirements (>> Oracle documentation). If you do need to add language-specific sorts, only add those that you definitely require.
  2. When starting one of Aurea CRM's modules, a message is displayed informing you that the necessary indices need to be added ("ADD").
  3. Switch to the SQL tool and click on the Rebuild NLS_SORT-Indexes to add the indices for the selected info area, >> SQL Tool. Click on Rebuild ALL NLS_SORT-Indexes to add indices for all info areas.
    Note: Aurea recommends always using the Rebuild ALL NLS_SORT Indexes option.

    Only those indices are affected that access text fields.

    Note: To remove an index that is no longer required, delete the corresponding value from the MM_NLS_SORT parameter. When starting one of Aurea CRM's modules, a message is displayed informing you that the indices need to be deleted ("REMOVE"). Click on either the Rebuild NLS_SORT-Indexes or Rebuild ALL NLS_SORT-Indexes buttons in the SQL tool.
  4. Assign a sort order to users and rights groups in the Configuration info area in the Rights module:

    Field

    Contents

    Category

    ORACLE

    Option

    NLS_SORT

    Text

    <Sort order>, e. g. ENGLISH

    Rep/Group

    Enter the desired rep or group

    You cannot assign the sort order to a station in the Configuration info area. In order to assign a sort order to a station, define the MM_NLS_SORT parameter when adding the tables.

    If no sort order has been assigned to a user (neither individually nor for the user's group or station), the default value is used (i.e. the first value entered under MM_NLS_SORT).

    If a user is assigned a sort order for which no index exists, an error message is displayed when Aurea CRM is started. The user can proceed, but uses the default value instead.

Note: If different sort orders (collation) are defined in the Configuration info area (>> ORACLE) and database, the sort order defined in the Configuration info area is used when evaluating conditions applied to string fields. Enter COLLATE=OFF in the mmdb.ini file (>> [MM ORA]) to use the sort order defined in the database.