List of Supported Translatable Fields
The following list contains all translatable fields supported in NetSuite.
It was compiled to provide specific information about translatable fields whose behavior may vary across NetSuite features.
Translatable Field; Translatable Field ID |
Usage — Leads to View |
Usage — Should lead to GROUP |
Known to create duplicate IDs unless the Best Practices are observed |
Lockable in Bundler |
Lockable in Manage T |
Notes |
Owner |
ENTRY_ ENTRY_ ENTRY_ ENTRY_ ENTRY_ |
E E E E E |
E |
NO |
YES |
Most fields are lockable. |
When you create an entry form, the following translatable fields that are not lockable are also created: 16, |
Suite |
FORM_ FORM_ FORM_ FORM_ FORM_ FORM_ FORM_ |
F F F F F F F |
F |
NO |
YES |
Most fields are lockable. |
When you create a form template, the following translatable fields that are not lockable are also created: 16, |
S |
S S |
S |
S |
NO |
These fields are not lockable even on Bundle level. |
These fields are not lockable even on Bundle level. |
— |
UI |
KPI_ K KPI_ KPI_ |
KPI_ K K |
KPI_ |
YES |
These fields are not lockable even on Bundle level. |
These fields are not lockable even on Bundle level. |
— |
UI |
T T |
T |
T |
NO |
YES |
YES |
— |
I |
W W W W W W |
W W W |
W |
NO |
YES |
Most fields are lockable. |
When you create one of these translatable fields, the following translatable field that cannot be locked is also created: 'CUSTOM FIELD LABEL' type (TF 16, 17) |
S |
C |
C |
CENTER |
NO |
This field is not lockable even on Bundle level. |
This field is not lockable even on Bundle level. |
— |
S |
C |
C |
— |
YES |
This field is not lockable even on Bundle level. |
This field is not lockable even on Bundle level. |
— |
S |
CENTER_ |
C |
— |
NO |
This field is not lockable even on Bundle level. |
This field is not lockable even on Bundle level. |
— |
S |
CUSTOM_ CUSTOM_ |
C |
FORMS, W |
NO |
YES |
NO |
— |
S |
CUSTOM_ CUSTOM_ |
C |
— |
NO |
Most fields are lockable, it depends on specific cases. |
NO |
— |
S |
CUSTOM_ CUSTOM_ |
C |
— |
NO |
These fields are not lockable even on Bundle level. |
These fields are not lockable even on Bundle level. |
— |
S |
C CUSTOM_ |
C |
?CUSTOM RECORD |
NO |
These fields are not lockable even on Bundle level. |
These fields are not lockable even on Bundle level. |
— |
S |
C |
C |
C |
NO |
YES |
YES |
— |
S |
C |
C |
C |
NO |
YES |
YES |
— |
S |
CUSTOM_ CUSTOM_ |
C |
CUSTOM_ |
Cannot be determined, the behavior is not finished on the owner’s side. |
YES |
Most fields are lockable. |
When you create one of these translatable fields, the following translatable fields that cannot be locked are also created: 19 All 20 All 48 All 43 AllTask Label 44 AllTask ShortName |
S |
CUSTOM_ CUSTOM_ (lead to CUSTOM_ |
C |
— |
NO |
NO |
NO |
— |
S |
SAVED_ S (leads to SAVED_ |
SAVED_ |
SAVED_ |
NO |
NO |
NO |
— |
I |
SAVED_ |
SAVED_ |
SAVED_ |
NO |
YES |
YES |
— |
SA: |
S |
S |
SAVED_ |
YES |
YES |
YES |
— |
SA: |
SAVED_ |
S |
SAVED_ |
YES |
YES |
YES |
— |
SA: |
SAVED_ SAVED_ |
S |
SAVED_ |
YES |
YES |
YES |
— |
SA: |
SAVED_ |
S |
SAVED_ |
YES |
YES |
YES |
— |
SA: |
SAVED_ |
S |
SAVED_ |
YES |
YES |
YES |
— |
SA: |
S |
SCRIPT_ |
— |
NO |
NO |
NO |
Internal issues with lockability |
R S |
SCRIPT_ S |
SCRIPT |
SCRIPT |
NO |
YES |
YES |
— |
S |
SCRIPT_ |
S |
SCRIPT |
YES |
YES |
YES |
— |
S |
CUSTOM_ TASK_ |
C TASK_ |
CUSTOM_ |
YES |
Depends on the type of usage |
NO |
This translatable field is often created as a by-product during creation of other translatable fields. |
— |
D DATASET_ DATASET_ DATASET_ |
D |
DATASET INSTANCE |
A collection is automatically generated when strings with these translatable fields are exported, therefore the duplicate ID issue cannot occur with them. |
These fields are not lockable even on Bundle level. |
These fields are not lockable even on Bundle level. |
— |
S |
REPORT_ REPORT_ REPORT_ REPORT_ |
REPORT, but now: Usr |
REPORT INSTANCE |
A collection is automatically generated when strings with these translatable fields are exported, therefore the duplicate ID issue cannot occur with them. |
These fields are not lockable even on Bundle level. |
These fields are not lockable even on Bundle level. |
— |
S |
CHART_ CHART_ CHART_ C C CHART_ CHART_ CHART_ |
CHART, but now: Usr |
CHART INSTANCE |
A collection is automatically generated when strings with these translatable fields are exported, therefore the duplicate ID issue cannot occur with them. |
These fields are not lockable even on Bundle level. |
These fields are not lockable even on Bundle level. |
— |
S |
W W |
W |
W |
A collection is automatically generated when strings with these translatable fields are exported, therefore the duplicate ID issue cannot occur with them. |
These fields are not lockable even on Bundle level. |
These fields are not lockable even on Bundle level. |
— |
S |
T T |
D |
DATAVIEW INSTANCE |
A collection is automatically generated when strings with these translatable fields are exported, therefore the duplicate ID issue cannot occur with them. |
These fields are not lockable even on Bundle level. |
These fields are not lockable even on Bundle level. |
— |
S |
For more information about the proper import and export process, see Best Practice for Exporting and Importing Strings From Translatable Fields.