Best Practice for Exporting and Importing Strings From Translatable Fields
When exporting strings containing certain translatable fields, you should not edit the records containing the exported strings from translatable fields to limit the number of possible issues.
If you edit a record containing exported translatable field of a certain type, a duplicate of the exported translatable field will be created and after import, translation will not longer be paired with the given translatable field and the field will not be translated.
For more information about the affected translatable fields, see the Known to create duplicate IDs unless the Best Practices are observed column in the List of Supported Translatable Fields.
You may choose not to follow the proposed process for fields which are not known to cause this issue, but as a rule of thumb, it is safer to always follow the preferred process.
See the preferred process for exporting and importing of translation strings from translatable fields:
To Export and Import Strings from Translatable Fields:
-
After completing your work on the respective records, close all the records which are to be exported.
-
Export all the desired strings and have them translated.
Warning:To avoid encountering issues, between exporting strings from certain translatable fields and importing their translations:
-
Do not edit the records containing the exported translatable field.
-
Do not open the records containing the exported translatable fields for editing, even if you are not going to change any parameter.
Failure to follow this warning may result in your translatable fields not being translated.
-
-
Import the translations back into NetSuite.
-
You may now edit records containing the translatable fields without any adverse effect on NetSuite translations.