Best Practice for Exporting and Importing Strings From Translatable Fields
When exporting strings with certain translatable fields, don't edit the records with those exported strings to avoid issues.
If you edit a record with an exported translatable field, a duplicate will be created. After import, the translation won't be paired with the field and it won't be translated.
You can skip this process for fields that don't cause issues, but it's usually safer to stick with 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:
-
When you're done working on the records, close all the ones you want to export.
-
Export the strings you need and translate them.
Warning:To avoid encountering issues, between exporting strings from certain translatable fields and importing their translations:
-
Don't edit the records with the exported translatable field.
-
Don't open the records with exported transltatable fields for editing, even if you won't change anything.
If you don't follow this warning, your translatable fields might not get translated.
-
-
Import the translations back into NetSuite.
-
No you can edit records with translatable fields without affecting NetSuite translations.