Set up a translation table

The required field in the translation table is Item ID. Optionally, you can map the Name field if you need to use it in the dashboard instead of what is mapped for the Item ID.

If you map other fields, they can only be used in the following cases:

  • Add them as data series in metric grids.

  • Map pins with geographical coordinates for the geo map component.

  • If the user filter is configured in Admin Console, you can assign this filter to the field in the translation table (use the Filter property on the Property Panel).

    For example, the user filter is configured only to Boston and Chicago as ship cities. In the translation table, you can map the Ship City field and assign this user filter to it. In the grid, the Ship City dimension only uses the translation table for these two cities of Boston and Chicago.

Translation tables can be of the two types:

  • Dynamic: Values are reloaded periodically.

  • Static: Mapped values are defined and do not change, such as 1 for Monday and 2 for Tuesday.

  1. On the Documents Tree, right-click Translation Tables and select New Translation table.
  2. Assign a name and select the translation table type: Dynamic or Static.
    • Dynamic: Values are reloaded periodically.

    • Static: Mapped values are defined and do not change, such as 1 for Monday and 2 for Tuesday.

  3. On the Mapping tab under Sources, click the Plus icon.
  4. In the New source type section, select Translation Table.
  5. In the New source type section, click the ellipsis button to navigate to and select the translation table.
  6. Click OK twice to return to the main mapping screen.

    A list of fields available within the selected translation table appears in the left column.

  7. Map the relevant information by dragging the field name in the left column and dropping it on the corresponding field name in the right column.

    The Start and End dates are only required to allow mappings from an ID to a name to vary over time. The only required fields are Item ID and Name. Other fields can be added and are available for display in a grid, but the primary purpose is to establish the mapping between the Item ID and the Name fields.

    You can use multiple data sources and derived fields to define a translation table in the same way as you define a record. See New records - join data sources.

    You can use data filters and custom queries to refine what is included in the translation table. Select the Filters and SQL tabs to access these options. See SQL queries for record.

    Use the Test tab to verify the translation table definition is working.

    Note The required field is ItemID. If you map other fields, you can use them in the following cases: add them as data series in metric grids or use them to map pins with geographical coordinates for the geo map component.

Create a static translation table

  1. On the Documents Tree, right-click Translation Tables and select New Translation Table.
  2. Assign a name and select the translation table type: Dynamic.
  3. On the Mapping tab under Sources, click the Plus icon.
  4. In the New source type section, select the data source. Click OK.
    A list of fields available within the selected translation table appears in the left column.
  5. Map the relevant information by dragging the field name in the left column and dropping it on the corresponding field name in the right column.

    The Start and End dates are only required to allow mappings from an ID to a name to vary over time. The only required fields are Item ID and Name. Other fields can be added and are available for display in a grid, but the primary purpose is to establish the mapping between the Item ID and the Name fields.

    You can use multiple data sources and derived fields to define a translation table in the same way as you define a record. See New records - join data sources.

    You can use data filters and custom queries to refine what is included in the translation table. Select the Filters and SQL tabs to access these options. See SQL queries for record.

    Use the Test tab to verify the translation table definition is working.

    Note The required field is ItemID. If you map other fields, you can use them in the following cases: add them as data series in metric grids or use them to map pins with geographical coordinates for the geo map component.

  6. Save the changes.

Create a dynamic translation table

  1. On the Documents Tree, right-click Translation Tables and select New Translation Table.
  2. Assign a name and select the translation table type: Static.
  3. Click Add New Data to add new Item IDs and names (for example, week days).

  4. Save the changes.