Set Tenant Translation Table
Learn about the API operation to set the tenant translation table
This operation sets the Tenant Translation Table. This table is used for a specified tenant. Tenant level i18n resources have higher priority than the Global level resources.
This internationalization API operation supports localization of label patterns, direction labels, error messages, and, customer-defined lookups. The labels, abbreviations, captions, and descriptions can be localized by modifying the UI configuration. For more information, see topic UI configuration at a glance.
ROLE_ADMIN_TENANT role or write permissions on the resources to use this API operation.Request
POST {TenantURL}/resources/i18n| Parameter | Required | Description | |
|---|---|---|---|
| Headers | Content-Type | Yes | Should be "Content-Type: application/json". |
Language | Yes | Language of the table. Format: xx-YY (e.g. ru-RU). | |
| Body | Yes | JSON object with Translation Table. | |
Response
Example Request
If the Tenant Translation Table is persisted successfully, then the response will contain the JSON of the saved Tenant Translation Table.
POST /reltio/tenantID/resources/i18n
Language: ru-RU
Body:
{
"Doctor {FirstName} {LastName} from {Address}": "Доктор медицины {FirstName} {LastName} из {Address}",
"has address": "имеет адрес"
}Example Response
{
"Doctor {FirstName} {LastName} from {Address}": "Доктор медицины {FirstName} {LastName} из {Address}",
"has address": "имеет адрес"
}Example Request with i18n error
If you want to indicate an i18n error with the number 4003, which signifies that the entity has dependent lookup validation issues, then make a POST request similar to this example.
POST /reltio/tenantID/resources/i18n
Language: fr
Body:
{
"error.4003" : "La recherche {0} ne correspond à aucune recherche par parenté spécifiée dans cette entité"
}