Overview
In legacy Construct, cell values could display translated values to the Language ID associated with their user account using a Translate checkbox feature that looked up display values from catalog tables.
Cloud Construct does not have the Translate checkbox feature. Instead, it offers the following alternatives to display translated values:
Updated Methodology
Approach A: Display Translated Values Directly
Create SQL view that JOINs the source table with lookup/catalog (translation) table. Include both code and translated display value in the same view. For example,
SELECT o.OrderID, o.OrderDate, o.StatusCode, s.StatusDisplay as Status_Display FROM Orders o LEFT JOIN OrderStatus s ON o.StatusCode = s.StatusCodeEdit the required WebApp.
In the WebApp Builder, access the required page’s grid container and configure the dataset to point the view above.
Include both StatusCode and Status_Display fields
Hide StatusCode column if not needed
Save and Preview the WebApp.
Grid displays translated text instead of code.
Approach B: Dependent List Box Filters
Create a SQL view that contains both the code (from the source view) and the translated values, then register it as a list box dataset.
Edit the required WebApp.
In the WebApp Builder, access the required page’s grid container and configure a list box field using the list box dataset.
Apply list box filter to bind the code from the source grid, for example
ListBox.StatusCode = Grid.StatusCodeSet the translated value as the list box Display value.
In the grid container, use the list box for the code column instead of the code column from the grid source dataset.
The column will display the translated value based on row's code. When the row data changes, the displayed value updates automatically.
Example Translation Scenarios
Code Value | Lookup Table | Translated Display |
|---|---|---|
"A" | OrderStatus | "Active" |
"P" | OrderStatus | "Pending" |
"C" | OrderStatus | "Closed" |
"US" | Countries | "United States" |
"CA" | Countries | "Canada" |