Integrating External Tables

To display additional data from another database in Aurea CRM (e.g. statistics of website visits, additional product information etc.) you can integrate external tables into the Aurea CRM data model.

Note: These external tables are available as read-only info areas in Aurea CRM.

Non-unicode tables are automatically converted to unicode.

To link an external table to the Aurea CRM data model:

  1. Create a new info area: In the Select Info Area Type dialog select the type matching the key of the external table.

    In this case you would have to select "root, primary index: int".

  2. Click OK.
  3. Select the External column.


  4. Enter the database, schema and name of the external table.
    Note: The external table must be accessible via the settings defined in the mmdb.ini file of your Aurea CRM win installation, i.e. it must be located on the same database server.
  5. Click OK.
  6. Select the Fields column.
  7. Delete the automatically generated fields (no. 4011-4016).
  8. Add the desired fields, see Adding New Fields.
    Note: Make sure the data types of the internal and external fields match since this is not automatically checked by the system.
  9. Select the DB Column column to define the "mapping" between external and internal fields:


  10. For each field select the field from the external table: Make sure you assign the unique key field(s) from the external table to the unique key field(s) of the new info area.
  11. Click OK.
  12. Click (OK) to close the Fields level.
  13. Select Test info area from the context menu:


    You can page through the data from the external table using the arrow buttons.

After applying the data model changes you can use the new info area in customizations like any other info area (links to other info areas, reference fields, configuring the info area for Aurea CRM web etc.).

Since info areas displaying data from external tables are read-only you do not need to define additional access rights for them.

Note: External tables are not communicated, i.e. an error message is displayed if the info area mapped to the external table is accessed by an offline client.