karlenigma
12/04/2023, 3:45 PMWatz
12/04/2023, 6:14 PMkarlenigma
12/04/2023, 6:15 PMBS
12/05/2023, 7:02 PMBS
12/05/2023, 7:29 PMkarlenigma
12/05/2023, 7:30 PMRyan Valizan
12/08/2023, 2:58 PMxml
<customrecordtype>
<name>customrecord_my_custom_record</name>
<label>My Custom Record</label>
<translations>
<translation locale="fr_CA">
<label>Mon Enregistrement Personnalisé</label>
</translation>
<translation locale="es_ES">
<label>Mi Registro Personalizado</label>
</translation>
</translations>
<fields>
<field>
<fieldid>custrecord_my_field</fieldid>
<label>My Field</label>
<translations>
<translation locale="fr_CA">
<label>Mon Champ</label>
</translation>
<translation locale="es_ES">
<label>Mi Campo</label>
</translation>
</translations>
<type>text</type>
</field>
<!-- Additional fields and translations as necessary -->
</fields>
<!-- Further custom record configuration -->
</customrecordtype>
In this XML snippet, <translations>
tags are used to define localized versions of the <label>
tags for both the custom record type and its fields. The locale attribute specifies the locale for which the translation is provided.
Note, while this example uses a structure that seems logical for defining translations within the custom record type definition, actual support for such a structure depends on the capabilities and limitations of the current version of SDF. If this approach is not supported, you may need to rely on scripts or other methods to handle translations dynamically.