Not all attributes can be used with multilingual translations. An attribute which cannot be used lacks the 'Translated' check box in the Object Type Customizer 'Attributes' tab.

An attribute can be translated if the following conditions are met:

• The attribute's object type has an artificial primary key (I.e. its primary key is one dedicated column)
• The attribute's object type is not a translation object type (In other words, it is not possible to translate translations.)
• The attribute does not have Client semantics

• The attribute does not have a value set (in such case the value set itself is translated using standard 'non-data' translations.

Regarding attribute type and length (max length limit is given in characters):

• The corresponding database column type is:
  • Oracle: CLOB, VARCHAR2(<=2000), CHAR(<=1000)
  • SQLServer: varchar(max), varchar(<=4000), char(<=4000)
  • DB2: CLOB, VARCHAR, CHAR

Additional limitation - attributes referred by customization

Even if the above conditions are met, attributes whose value is referred by Valuemation customization should not be translated. This concerns, for example, identification attributes for authorization by attribute value, rule condition or catalog rendering condition.

This limitations is caused by possible difference between the customer's and the standard main language of data which might cause problems with future functionality updates.