Skip to main content

What’s New

Qrvey 8.7
Version 8.7 of the Qrvey platform is now available to customers! This version includes new features including area charts, the ability to pivot and export data, as well as numerous bug fixes and performance improvements.
Learn More
Qrvey 8.6
Version 8.6 of the Qrvey platform is now available to customers. This version includes several new feature enhancements and performance improvements.
Learn More
Required Update for 8.5.1
Attention 8.5.1 customers: for any 8.5.1 instance deployed prior to 08/05/2024, an update is required to ensure you are running the latest images.
Learn More
Qrvey 8.5
Version 8.5 (LTS) of the Qrvey platform is now available to customers. This version includes several new features and performance improvements.
Learn More
End-of-life Schedule
We've added a new article that lists the features and endpoints that have been scheduled for deprecation. All features and endpoints will be supported for (1) year after the release date of the LTS version that contains the alternative.
Learn More
Version: 8.0

Configuring Dynamic Labels For Datasets

Introduction​

Qrvey supports a process for displaying text in any number of languages.

There are two types of text:

  • Static Text is built into the Qrvey product pages. These are titles, labels, tooltips, buttons, menus, and such.
  • Dynamic Text is the text that is entered by Qrvey Composer users. This is text such as Dataset names and Dataset column names.

Translated values are entered and stored in a Google spreadsheet. The spreadsheet contains a key for each text segment. The translation process involves entering values for each language for each key.

Based on this definition, UI components that use static text are known to the system. For example there is a button on the toolbar of the Page Builder that is titled “Publish Page”. If you generate the Translation Spreadsheet using the steps in the Internationalization, Step By Step article, you can find a predefined key toolbar.publish_page.label in the pagebuilder domain and its original source value is set to “Publish Page”.

When it comes to dynamic text, such as dataset names and their column aliases, they will be different from instance to instance and therefore the keys cannot be predefined in the system and have to be configured by the primary users.

At this time Qrvey supports dynamic text tokens (i18n tokens) in the Dataset design step in Qrvey Composer. This article explains the process of configuring a dataset so its name and column aliases are translated.

Setting i18n Tokens For Datasets​

All datasets in Qrvey are named by the composer user that creates them and their columns can also be aliased from the dataset design screen. If you wish for the name of any dataset and/or its columns to appear differently for end users of different cultures, enable and use the i18n tokens for the dataset in question. On the dataset design screen select the 3-dot popup menu from the top-right side of the screen and enable Label Internationalization. This prompts the system that the dataset and its columns’ names shall be added to the Translation Spreadsheet with their keys and their existing names as the original source values.

internationalization

Tokens are suggested for each name based on the name itself. For example a column named “age” will be assigned the token {{i18n.age}}. In order to view and optionally modify the assigned token, click the toggle button on the top-right corner of the screen to the { } position. This changes the displayed value to show the assigned tokens.

Tokens appear in the UI like: {{i18n.myTokenKey}} Click in each field to change the “key” part of any token. If a similar token already exists, the system will suggest it and you can select any of the suggested tokens to reuse.

Once the Label Internationalization has been turned on, keys have optionally been modified, and changes to the dataset have been applied, remember to run (or re-run) the steps in sections 3-6 as described in the Internationalization, Step By Step article, to add the new keys to the Translation Spreadsheet, translate their value, and publish them for use at runtime.