Language Mapping

This feature lets you translate titles, labels, and other descriptive text in your dashboards into multiple languages

Pre-requisite: Configure the Language Mapping part in the Admin module before using Language Mapping for a dashboard in Designer.

Prepare your dashboard text for translation

  1. Open a saved dashboard using the Designer plugin.

  2. In Title properties (and other descriptive fields), ensure the text to be translated is wrapped in curly braces {}.

    • Example:

      • Title: {Monthly Sales Dashboard}

      • X-axis: {Month}

      • Y-axis: {Revenue}

      • Tooltip: {Total revenue}

Please Note:

  • Use {} for all descriptive text you want translated (e.g., Tooltip, Description of X and Y-Axis, etc.).

  • Use the Data Set Properties to configure the Categories and Series description for language mapping.

Configure Language Properties (Dashboard level)

  1. Open the Dashboard Properties Panel and find Language Properties.

  2. Enable the Language Mapping (check the box).

  3. (Optional) Hide the Curly Braces (check the box) to suppress {} in the runtime UI.

  4. Click the mapping icon to select a mapping option.

    • The Language Mapping Selection window opens.

    • Choose a language from the Mapping List drop-down.

    • Click Save.

Script reference (component/dashboard)

  1. Open the Script window for a Component (or the dashboard, if applicable).

  2. Make sure the desired language’s name is mentioned in the script (as required by your environment).

    • Example pattern (pseudocode):

      // Ensure the target language token/name is set/used
// setDashboardLanguage('French'); // example only – use your environment’s method

  3. Click Preview.

Supported areas for Language Settings

Language Mapping can be used for (including but not limited to):

  • Title and Subtitle description

  • X-axis and Y-axis description (including second Axis description)

  • Inbuilt Legends, Timeline Legends

  • Legend component and static legends

  • Title of filters

  • Header name of Grids

  • Pie chart without a category: Legends

  • Tooltips and custom tooltip

  • Export, Filter Saver, URL button, Bullet, Gauge, Semi gauge titles

Notes:

  • Old dashboards do not open while using the Mapping option. Create a new dashboard to access this functionality.

  • Keep component names, dataset Display Names, and braced text consistent to ensure correct translation mapping.

  • If you use Hide the Curly Braces, the braces are hidden at runtime, but you must still keep text wrapped {} in the configuration.

Tips:

  • Standardize phrasing across dashboards so one mapping entry covers many places (e.g., reuse {Revenue} everywhere).

  • For dataset-driven labels, set human-friendly Display Name values in Data Set Properties and wrap them in {} If they’re descriptive text.

  • Test multiple languages in Preview and verify axes, legends, tooltips, and grid headers.

Troubleshooting

  • Text is not translated:

    • Confirm the text is inside {}.

    • Verify Language Mapping is enabled and a Mapping List language is selected and saved.

    • Check that the script references the correct language name/token (if required).

  • Some labels translate, others don’t:

    • Ensure those labels are descriptive text and wrapped in {} (axis, legends, tooltips).

    • Verify Data Set Properties display names for Categories/Series.

  • Braces visible at runtime:

    • Enable Hide the Curly Braces in Language Properties.

  • Legacy dashboards fail to open with mapping:

    • Recreate as a new dashboard and reapply {} braces and mappings.

PreviousGeo MappingNextLegend Mapping